ContextQMD
Back to Ag Grid

JIRA Skill

external/ag-shared/prompts/skills/jira/SKILL.md

100.0.04.3 KB
Original Source

JIRA Skill

Unified skill for creating, estimating, and analysing JIRA tickets across AG products.

Step 0: Verify Atlassian MCP Connection

Before doing anything else, verify the Atlassian MCP is available by calling mcp__atlassian__atlassianUserInfo. If the tool is not available, returns an error, or the MCP server is not connected:

Hard stop. Output the following and do not proceed:

Cannot proceed — Atlassian MCP is not connected.

This skill requires the Atlassian MCP server to interact with JIRA.
Please ensure the MCP connection is configured and active, then retry.

Do not attempt to work around the missing connection or produce partial results.

Product Detection

Detect the product from the repository context:

  • AG Charts: repos containing ag-charts-community — read products/charts.md
  • AG Grid: repos containing ag-grid-community — read products/grid.md
  • AG Studio: repos containing ag-studio-core or with project key ST — read products/studio.md

Read the appropriate product file before proceeding with any workflow.

Workflow Routing

Based on user intent, read the corresponding workflow file (in the workflows/ subdirectory of this skill):

IntentKeywordsWorkflow
PlanIn plan mode, drafting a plan that includes JIRA ticket creationworkflows/plan.md
Create"create a JIRA", "file a bug", "write up a ticket", "log this issue"workflows/create.md
Estimate"estimate", "size", "analyse complexity", "how long", "effort"workflows/estimate.md
Analyse"analyse this issue", "product analysis", "UX analysis", "propose solutions"workflows/analyze.md

Read the workflow file, then follow its instructions.

Shared Reference

Atlassian Cloud ID

All API calls use: 1565837d-d6d1-4228-bcb2-4cb74df700f2

Required Fields

FieldAPI NameFormat
ProjectprojectKey"AG" (or "ST" for Studio)
TypeissueTypeName"Bug" or "Task"
Summarysummary"[Product] Title" (prefix from product file)
DescriptiondescriptionSee templates
ComponentcomponentsFrom product file
Trackcustomfield_10501See track values below

Track Values (customfield_10501)

ValueIDUse For
Bug10401Bug fixes
Feature Request10400New features
Improvement10403Enhancements
Housekeeping10404Tech-debt, refactoring
Doc change10402Documentation updates

Format: [{"value": "Bug"}] or [{"id": "10401"}]

Each ticket has exactly one track value. Never set multiple track values on a single ticket.

Description Formatting

  • Use plain numbered lists: 1. Item (not # wiki markup).
  • Indent sub-items with 4 spaces: 1. Sub-item.
  • End numbered items with periods.
  • Bold: **text**.
  • Code: backticks.
  • URLs: Paste raw URLs directly (JIRA auto-links them); avoid [text](url) markdown links.
  • Empty sections: Just N/A.
  • No comments — all info in description.
  • When creating tickets from analysis/research documents, distil to decisions and recommendations only. Do not reproduce full analysis in the description — link to the analysis document in the "Design Documents" section instead.
  • Related tickets: Use formal JIRA issue links (not ticket keys in description text). When a fix resolves downstream bugs, use "Blocks" link type. Use mcp__atlassian__createIssueLink to create links after ticket creation.

Templates

  • Feature/Task: templates/feature-task.md (12-section numbered format)
  • Bug: templates/bug.md (TC-based format)

Follow the exact structure from the template. Do not use free-form markdown headers (##), tables, or code blocks for top-level structure.

Troubleshooting

Discovering required fields: Use mcp__atlassian__getJiraIssueTypeMetaWithFields with cloudId, projectIdOrKey: 'AG', issueTypeId: '10105' (Task).

Common errors:

  • "Track/Components is required": Add customfield_10501 and/or components array.
  • Ticket in Backlog instead of To Do: Transition to "To Do" using transition ID 141 after creation.
  • Do not set in_kanban label: Managed automatically — never add to labels field.