home / skills / dmmulroy / .dotfiles / jira-tool

jira-tool skill

safe

This skill helps you manage Jira tickets from creation to closure, automating transitions and updates for faster issue tracking.

npx playbooks add skill dmmulroy/.dotfiles --skill jira-tool

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

3.6 KB

---
name: jira-tool
description: Create, update, transition, and manage Jira tickets. Use when working with Jira issues, tracking work, or automating ticket workflows.
---

# Jira Tool

CLI for Jira operations via Cloudflare Access authentication.

## Quick Reference

| Task | Command |
|------|---------|
| Create ticket | `scripts/jira-tool.sh create -p PROJECT -s "Summary" [-t Type] [-d "Desc"] [-l labels]` |
| Get ticket | `scripts/jira-tool.sh get ISSUE-KEY` |
| Update ticket | `scripts/jira-tool.sh update ISSUE-KEY [-s "Summary"] [-d "Desc"] [-a user]` |
| Add comment | `scripts/jira-tool.sh comment ISSUE-KEY "Comment body"` |
| Transition | `scripts/jira-tool.sh transition ISSUE-KEY [STATUS]` |
| Close ticket | `scripts/jira-tool.sh close ISSUE-KEY` |
| Assign | `scripts/jira-tool.sh assign ISSUE-KEY [username]` |
| Search | `scripts/jira-tool.sh search "JQL query" [max]` |
| Auth status | `scripts/jira-tool.sh status` |

## Authentication

Auth is automatic via `cloudflared`. On first use or token expiry:
- Browser opens for Cloudflare Access login
- Token valid 24h

Check status: `scripts/jira-tool.sh status`

## Commands

### Create

```bash
scripts/jira-tool.sh create \
  -p PROJECT \
  -s "Fix authentication bug" \
  -t Bug \
  -d "Detailed description" \
  -l "urgent,backend" \
  --priority High \
  -a username
```

Required: `-p` (project), `-s` (summary)
Optional: `-t` (type, default: Task), `-d` (description), `-l` (labels), `--priority`, `-a` (assignee), `--parent` (for Sub-task), `--epic` (link to epic)

#### Sub-tasks

```bash
# Create a sub-task under an existing issue
scripts/jira-tool.sh create -p PROJ -s "Subtask summary" -t Sub-task --parent PROJ-123
```

#### Link to Epic

```bash
# Create task linked to an epic
scripts/jira-tool.sh create -p PROJ -s "Task summary" --epic PROJ-100
```

**Note:** Assignee uses Jira username (not email). Find via `search` on existing tickets.

### Get

```bash
scripts/jira-tool.sh get PROJ-123
```

Returns JSON with summary, status, assignee, priority, description, labels.

### Update

```bash
scripts/jira-tool.sh update PROJ-123 -s "New summary" -d "New desc" -a newuser
```

### Comment

```bash
scripts/jira-tool.sh comment PROJ-123 "Fixed in commit abc123"
```

### Transition

List available transitions:
```bash
scripts/jira-tool.sh transition PROJ-123
```

Transition to status:
```bash
scripts/jira-tool.sh transition PROJ-123 "In Progress"
```

### Close

Tries common close statuses (Done, Closed, Resolved, Complete):
```bash
scripts/jira-tool.sh close PROJ-123
```

### Assign

```bash
scripts/jira-tool.sh assign PROJ-123 username   # assign
scripts/jira-tool.sh assign PROJ-123 -1         # unassign
```

### Search

```bash
scripts/jira-tool.sh search "project = DEVTOOLS AND status = Open" 50
```

### Delete

```bash
scripts/jira-tool.sh delete PROJ-123
```

## Common JQL Queries

| Query | JQL |
|-------|-----|
| My open tickets | `assignee = currentUser() AND status != Done` |
| Project backlog | `project = PROJ AND status = "To Do"` |
| Recently updated | `project = PROJ AND updated >= -7d` |
| High priority | `priority in (High, Highest) AND status != Done` |

## Output

Most commands return JSON. Parse with `jq`:

```bash
scripts/jira-tool.sh get PROJ-123 | jq '.fields.status.name'
scripts/jira-tool.sh search "assignee = currentUser()" | jq '.issues[].key'
```

## Typical Workflow

```bash
# Create and start work
scripts/jira-tool.sh create -p PROJ -s "Implement feature X" -t Task
scripts/jira-tool.sh transition PROJ-456 "In Progress"

# Update progress
scripts/jira-tool.sh comment PROJ-456 "Initial implementation done"

# Complete
scripts/jira-tool.sh close PROJ-456
```

Overview

This skill provides a CLI for creating, updating, transitioning, and managing Jira tickets using Cloudflare Access authentication. It exposes common Jira operations as simple shell commands and returns JSON output suitable for scripting and pipelines. Use it to automate workflows, query issues with JQL, and integrate Jira actions into CI/CD or local tooling.

How this skill works

Commands are invoked via a shell script that authenticates through cloudflared and the Cloudflare Access flow; the first run opens a browser for login and tokens are valid for 24 hours. The tool maps common Jira REST operations (create, get, update, comment, transition, assign, search, delete) to short commands and prints JSON for easy parsing with tools like jq. Transitions can be listed or executed by name, and create supports types, priorities, labels, epics, and parent links for sub-tasks.

When to use it

Creating new Jira issues from scripts or local workflows
Automating status transitions and ticket lifecycle steps
Adding comments, assigning, or updating tickets programmatically
Running JQL searches and extracting issue data for reports
Integrating Jira actions into CI/CD, deployment, or developer tooling

Best practices

Use the search command to look up usernames or existing issues before assigning or linking.
Parse JSON output with jq in scripts to handle fields like status, assignee, and key reliably.
Prefer explicit transitions by name; list available transitions first to avoid state errors.
Provide required flags (project -p and summary -s) when creating issues to prevent failures.
Keep cloudflared session active (status command) and re-authenticate in the browser when prompted.

Example use cases

Create a task and immediately transition it to In Progress from a CI job.
Attach a deployment comment to a ticket: scripts/jira-tool.sh comment PROJ-123 "Deployed to staging".
Batch update: search with JQL then loop over results to assign or set priority.
Create a sub-task under an existing issue for breaking down work items.
Close stale issues by searching recently inactive tickets and running the close command.

FAQ

How does authentication work?

Authentication uses cloudflared and Cloudflare Access. The first use or token expiry opens a browser for login; tokens last 24 hours.

How do I find a Jira username for assignee flags?

Search existing tickets or use the search command to list issues and inspect the assignee field; the CLI expects Jira usernames, not email addresses.