Jira Ticket Manager

Jira Ticket Manager Skill Instructions

Use curl to interact with the Jira REST API. All responses are saved locally for reliable parsing.

Pre-Flight Check

Verify environment variables are set (source the shell profile first):

source ~/.zshrc 2>/dev/null || source ~/.bashrc 2>/dev/null; echo "JIRA_URL: ${JIRA_URL:-(not set)}"; echo "JIRA_USER: ${JIRA_USER:-(not set)}"; echo "JIRA_TOKEN: ${JIRA_TOKEN:+set}"

If variables are missing, guide the user to add them to ~/.zshrc:

# Appends to ~/.zshrc
printf '\nexport JIRA_URL="https://company.atlassian.net"\nexport JIRA_USER="your-email@company.com"\nexport JIRA_TOKEN="your-api-token"\n' >> ~/.zshrc && source ~/.zshrc

Do NOT ask users to paste credentials directly—the token should stay in their shell profile.

Data Storage

API responses are saved to .claude/temp/jira-ticket-manager/ for reliable parsing (Jira responses are 30KB+ and get truncated when piped).

First-time setup:

mkdir -p .claude/temp/jira-ticket-manager

Files stored:

• {TICKET-KEY}.json - Individual ticket data (e.g., PROJ-123.json)
• search-latest.json - Most recent search results
• my-tickets.json - Current user's tickets

Users can delete the folder anytime to clear cached data.

Command Pattern

Every command must source the shell profile first:

source ~/.zshrc 2>/dev/null || source ~/.bashrc 2>/dev/null; <curl command>

All examples below omit this prefix for brevity—always include it.

Operations

Get Ticket

Step 1: Fetch and save

curl -s -u "$JIRA_USER:$JIRA_TOKEN" "$JIRA_URL/rest/api/2/issue/PROJ-123" -o .claude/temp/jira-ticket-manager/PROJ-123.json

Step 2: Parse

jq '{
  key: .key,
  summary: .fields.summary,
  status: .fields.status.name,
  type: .fields.issuetype.name,
  priority: .fields.priority.name,
  assignee: .fields.assignee.displayName,
  reporter: .fields.reporter.displayName,
  created: .fields.created[0:10],
  updated: .fields.updated[0:10],
  description: .fields.description,
  parent_key: .fields.parent.key,
  parent_summary: .fields.parent.fields.summary
}' .claude/temp/jira-ticket-manager/PROJ-123.json

Output format:

PROJ-123: Summary here
Status: In Progress | Type: Bug | Priority: High
Assignee: John Doe | Reporter: Jane Smith
Created: 2024-01-15 | Updated: 2024-01-20
Parent: PROJ-100 - Epic Name

Description:
[description text]

Search Tickets

Step 1: Fetch and save

curl -s -u "$JIRA_USER:$JIRA_TOKEN" -G \
  --data-urlencode 'jql=project = PROJ AND status = Open' \
  --data-urlencode 'maxResults=20' \
  --data-urlencode 'fields=key,summary,status,assignee,priority' \
  "$JIRA_URL/rest/api/3/search/jql" -o .claude/temp/jira-ticket-manager/search-latest.json

Step 2: Parse

jq '.issues[] | {key: .key, summary: .fields.summary, status: .fields.status.name, assignee: .fields.assignee.displayName, priority: .fields.priority.name}' .claude/temp/jira-ticket-manager/search-latest.json

Output as a table for user.

My Tickets

Step 1: Fetch and save

curl -s -u "$JIRA_USER:$JIRA_TOKEN" -G \
  --data-urlencode 'jql=assignee = currentUser() AND status != Done ORDER BY updated DESC' \
  --data-urlencode 'maxResults=20' \
  --data-urlencode 'fields=key,summary,status,priority,updated' \
  "$JIRA_URL/rest/api/3/search/jql" -o .claude/temp/jira-ticket-manager/my-tickets.json

Step 2: Parse

jq '.issues[] | {key: .key, summary: .fields.summary, status: .fields.status.name, priority: .fields.priority.name, updated: .fields.updated[0:10]}' .claude/temp/jira-ticket-manager/my-tickets.json

Create Ticket

curl -s -u "$JIRA_USER:$JIRA_TOKEN" \
  -X POST -H 'Content-Type: application/json' \
  -d '{
    "fields": {
      "project": {"key": "PROJ"},
      "summary": "Ticket summary here",
      "description": "Detailed description here",
      "issuetype": {"name": "Bug"}
    }
  }' \
  "$JIRA_URL/rest/api/2/issue" | jq '{key: .key, self: .self}'

Issue types: Task, Bug, Story, Epic, Sub-task (varies by project)

Optional fields: "priority": {"name": "High"}, "assignee": {"accountId": "..."}, "labels": ["label1"]

After creation, report: "Created PROJ-123: [summary]" with link.

Update Ticket

curl -s -u "$JIRA_USER:$JIRA_TOKEN" \
  -X PUT -H 'Content-Type: application/json' \
  -d '{"fields": {"summary": "Updated summary"}}' \
  "$JIRA_URL/rest/api/2/issue/PROJ-123"

PUT returns empty on success (HTTP 204). Verify by fetching the ticket.

Add Comment

curl -s -u "$JIRA_USER:$JIRA_TOKEN" \
  -X POST -H 'Content-Type: application/json' \
  -d '{"body": "Comment text here"}' \
  "$JIRA_URL/rest/api/2/issue/PROJ-123/comment" | jq '{id: .id, created: .created}'

Transition Ticket

Step 1: Get available transitions

curl -s -u "$JIRA_USER:$JIRA_TOKEN" \
  "$JIRA_URL/rest/api/2/issue/PROJ-123/transitions" | jq '.transitions[] | {id: .id, name: .name}'

Step 2: Apply transition

curl -s -u "$JIRA_USER:$JIRA_TOKEN" \
  -X POST -H 'Content-Type: application/json' \
  -d '{"transition": {"id": "21"}}' \
  "$JIRA_URL/rest/api/2/issue/PROJ-123/transitions"

Transition IDs vary by project—always fetch available transitions first.

Get Comments

curl -s -u "$JIRA_USER:$JIRA_TOKEN" \
  "$JIRA_URL/rest/api/2/issue/PROJ-123/comment" | jq '.comments[] | {author: .author.displayName, created: .created[0:10], body: .body}'

Error Handling

If a response contains errorMessages or errors, it failed. Common errors:

Output Guidelines

1. Be concise: Show key fields, not raw JSON
2. Format dates: Use [0:10] slice for YYYY-MM-DD
3. Link tickets: $JIRA_URL/browse/PROJ-123
4. Include parent: Show parent key and summary when present

URL Parsing

Extract ticket keys from URLs: