ChatGPT Prompts for Jira (Tickets, Boards, JQL)

Convert idea into Jira user story. Idea: [paste]. Output: title, description, "As a / I want / So that" format, acceptance criteria (3-5 bullets, testable), edge cases, dependencies, estimate placeholder. Story-format = clearer requirements.

Bug report for [observed behavior]. Output: title (specific symptom), environment (browser, OS, version), steps to reproduce (numbered), actual vs expected, screenshots/logs placeholder, severity, priority. Bug reports vague = wasted dev time.

Break [epic] into stories. Output: 5-10 stories (sized for sprint), dependencies between, sequencing, risks, acceptance criteria per story. Epics-with-no-stories = stuck.

[Paste AC draft]. Polish: testable (yes/no answer), specific (no ambiguity), complete (covers happy path + edge cases), independent (each criterion standalone). Bad AC = endless rework cycles.

JQL for [question — "all bugs assigned to me created last week"]. Output: JQL query, explanation, common variations, save as filter. JQL = power-user search.

Build JQL filter library for [team]. Common needs: my work, blocked tickets, sprint scope, recently changed, customer-reported. Per filter: JQL, name, who uses, sharing. Saved filters = compounded productivity.

Build Jira dashboard with [metrics]. Output: gadget per metric, JQL backing each, filter dependencies, audience-tuned. Dashboards = visibility without nagging.

Velocity + burndown reports for [team]. Output: which Jira reports help, configuration, what to look for (capacity issues, scope creep), how to discuss in retros. Data-driven sprint conversations.

Configure Scrum/Kanban board for [team]. Output: columns (To Do, In Progress, In Review, Done — adjust per team), filter, swimlanes (by epic, by assignee, etc.), card layout. Board = team's daily UI.

Sprint planning meeting agenda. Inputs: backlog, velocity, capacity. Output: plan agenda, ticket selection criteria, capacity calculation, commitment + stretch, risks discussed. Sprint planning quality predicts sprint quality.

Daily standup using Jira. Output: each person walks board (their tickets In Progress), blockers flagged on tickets (not just verbal), action items go to tickets. Visual standup beats verbal.

Sprint retrospective format using Jira data. Output: agenda — what we shipped (Jira data), what worked, what didn't, action items (created as Jira tickets). Specific actions vs vague feelings.

Design Jira workflow for [issue type]. Output: states (To Do → In Progress → In Review → Done), transitions, validators (who can transition), conditions, post-functions. Workflow = process enforcement.

Automation rule for [scenario — auto-assign, transition on PR merged, notify on overdue]. Output: trigger, conditions, actions. Jira Automation rules = no-code workflow.

Integration strategy for Jira with [tools — GitHub, Slack, Confluence]. Output: which integrations matter (PR linkage, channel notifications, doc linkage), config, data flow, security. Integration = unified tool stack.