agentsclimarketplace

Jira integration

Skill event4u-app/agent-config/dist/agent-src/skills/jira-integration

Use when the user says "check Jira", "create ticket", "update issue", or needs JQL queries, ticket transitions, or branch-to-ticket linking.From its SKILL.md

Install
npx -y skills add event4u-app/agent-config --skill jira-integration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.1 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

Jira Skill

When to use

Use this skill when:

  • Reading a Jira ticket for context (bug reports, feature requests)
  • Creating new Jira issues from discovered bugs or planned work
  • Transitioning ticket status (e.g., "In Progress" → "In Review")
  • Writing JQL queries to find related issues
  • Linking branches or PRs to Jira tickets

Do NOT use when:

  • GitHub Issues (use github-api tool directly)
  • Linear or other issue trackers

Procedure: Work with Jira

  1. Identify action — Search, read, create, update, or transition a ticket?
  2. Use the correct endpoint — See API table below.
  3. Execute — Make the API call with required fields.
  4. Verify — Confirm the response contains expected data or the ticket was updated.
ToolPurpose
jira-integration (GET /search/jql)Search issues with JQL
jira-integration (GET /issue/{key})Read a specific ticket
jira-integration (POST /issue)Create a new ticket
jira-integration (PUT /issue/{key})Update a ticket
jira-integration (GET /issue/{key}/transitions)Get available status transitions
jira-integration (POST /issue/{key}/transitions)Transition ticket status
jira-integration (POST /issue/{key}/comment)Add a comment
jira-integration (GET /project)List projects
jira-integration (GET /field)List available fields (check before writing JQL)

Branch-to-ticket detection

Extract ticket IDs from branch names automatically:

feat/DEV-1234/user-notifications  →  DEV-1234
fix/DEV-5678/null-pointer         →  DEV-5678
hotfix/DEV-999/critical-fix       →  DEV-999

Pattern: [A-Z]+-[0-9]+ anywhere in the branch name.

Use git branch --show-current to detect, then fetch the ticket:

jira GET /issue/DEV-1234

JQL patterns

Common queries

# My open tickets
assignee = currentUser() AND status != Done ORDER BY priority DESC

# Tickets in current sprint
project = DEV AND sprint in openSprints() AND assignee = currentUser()

# Recently updated bugs
project = DEV AND type = Bug AND updated >= -7d ORDER BY updated DESC

# Tickets by component
project = DEV AND component = "Import" AND status != Done

Tips

  • Always check available fields first: GET /field
  • Use currentUser() for the authenticated user
  • Use sprint in openSprints() for current sprint
  • JQL is case-insensitive for field names but case-sensitive for values

Creating tickets

Required fields

Always check issue types first: GET /issue/createmeta/{project}/issuetypes

Minimum fields for creation:

  • project — project key (e.g., DEV)
  • issuetype — issue type (Bug, Task, Story, etc.)
  • summary — short title

Description format (ADF)

Jira uses Atlassian Document Format for descriptions:

{
  "version": 1,
  "type": "doc",
  "content": [
    {
      "type": "paragraph",
      "content": [
        { "type": "text", "text": "Description text here." }
      ]
    }
  ]
}

Attribution

Always add attribution when creating issues or comments:

Co-authored by Augment Code

With link to https://www.augmentcode.com/?utm_source=atlassian&utm_medium=jira_issue&utm_campaign=jira

Status transitions

Before transitioning, always get available transitions first:

GET /issue/DEV-1234/transitions

Then transition with the correct ID:

POST /issue/DEV-1234/transitions
{ "transition": { "id": "31" } }

Important: Never transition without explicit user permission (see rules/no-commit.md — same principle applies to ticket status changes).

Linking to PRs

When creating PRs, include the Jira ticket in:

  • Branch name: feat/DEV-1234/description
  • PR title: feat(DEV-1234): description
  • PR description: Link to the ticket

Related

  • Skill: bug-analyzer — uses Jira as input source for bug investigation
  • Skill: feature-planning — uses Jira for feature context
  • Command: /bug-investigate — auto-detects Jira tickets from branch
  • Command: /feature-plan — auto-detects Jira tickets from branch
  • Rule: no-commit.md — never change ticket status without permission

Output format

  1. Jira ticket data presented in structured format
  2. Ticket key, summary, status, and relevant fields

Gotcha

  • Jira field names are case-sensitive in JQL — status works, Status doesn't.
  • Don't create duplicate tickets — always search first with JQL before creating.
  • The model tends to forget that Jira description uses ADF (Atlassian Document Format), not Markdown.
  • accountId is required for assignee — display name alone doesn't work in the API.

Do NOT

  • Do NOT change ticket status without explicit user permission.
  • Do NOT create tickets without checking for duplicates.

Auto-trigger keywords

  • Jira
  • ticket
  • issue
  • JQL
  • workflow transition
  • sprint

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.