ChatGPT Prompts for Jira (Tickets, Boards, JQL)
20 copy-paste ChatGPT prompts for Jira: ticket writing, board configuration, JQL query mastery, sprint management, and the workflows that engineering teams actually run on.
In short: This page contains 16 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Ticket Writing
4 promptsUser Story from Idea
1/16✨ What it does
ChatGPT turns [paste] into a Jira user story with title, description, As a / I want / So that, 3-5 testable acceptance criteria, edge cases, dependencies, and an estimate placeholder. Paste the idea, then create the ticket and fill the estimate with the team.
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.
Pro tip: Vague tickets ("fix the dashboard") = endless rework. User-story format with testable AC = clear definition of done. Saves engineering cycles.
Bug Report Template
2/16✨ What it does
ChatGPT writes a bug report for [observed behavior] with a specific title, environment, numbered repro steps, actual versus expected, screenshot or log placeholders, severity, and priority. Fill environment and steps, then attach a real screenshot before you file it.
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.
Pro tip: Bug reports without reproduction steps = "works on my machine." Numbered specific steps = engineer reproduces in 5 min vs 50 min of guessing.
Epic Breakdown
3/16✨ What it does
ChatGPT breaks [epic] into 5-10 sprint-sized stories with dependencies, sequence, risks, and acceptance criteria per story. Create the stories under the epic, then sequence the ones that block the rest.
Break [epic] into stories. Output: 5-10 stories (sized for sprint), dependencies between, sequencing, risks, acceptance criteria per story. Epics-with-no-stories = stuck.
Pro tip: Epic without story breakdown = overwhelmed team. Story breakdown = ship-able increments. Most epics fail at decomposition; the discipline matters.
Acceptance Criteria Polish
4/16✨ What it does
ChatGPT polishes [Paste AC draft] so each line is testable, specific, complete for happy path plus edges, and standalone. Paste the draft, then replace any vague line before the ticket is played.
[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.
Pro tip: AC like "should work properly" = useless. AC like "When X clicks Y, system does Z within 1s" = testable. Specificity = clear definition of done.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
JQL Queries
4 promptsJQL from Question
5/16✨ What it does
ChatGPT writes JQL for [question - "all bugs assigned to me created last week"], with the query, an explanation, common variations, and how to save it as a filter. Type your question, then save the filter after you confirm the results.
JQL for [question — "all bugs assigned to me created last week"]. Output: JQL query, explanation, common variations, save as filter. JQL = power-user search.
Pro tip: Most users use Jira navigator (slow). JQL = specific filter in seconds. "assignee = currentUser() AND status = Open" = your work today.
Reusable Filter Library
6/16✨ What it does
ChatGPT builds a JQL filter library for [team] covering my work, blocked tickets, sprint scope, recently changed, and customer-reported, with name, who uses it, and sharing. Save the first two filters, then share them with the project.
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.
Pro tip: Saved filters reusable across team. Build 10 common ones; team uses forever. Most teams re-craft queries; library = institutional speed.
Dashboard Query Strategy
7/16✨ What it does
ChatGPT designs a Jira dashboard for [metrics] with a gadget per metric, backing JQL, filter dependencies, and audience tuning. Add the gadgets, then open the dashboard as that audience to confirm it loads.
Build Jira dashboard with [metrics]. Output: gadget per metric, JQL backing each, filter dependencies, audience-tuned. Dashboards = visibility without nagging.
Pro tip: Status meetings replaced by good dashboard. Real-time visibility = no "where are we?" questions. Investment in dashboards pays back across years.
Velocity + Burndown
8/16✨ What it does
ChatGPT plans velocity and burndown reporting for [team]: which Jira reports to use, configuration, what capacity issues and scope creep look like, and how to talk about them in retro. Open this sprint's burndown, then bring one chart to the next retro.
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.
Pro tip: Velocity tracked across sprints = capacity baseline. Burndown reveals: scope crept, team overloaded, holidays missed. Retros use this data; without = guesswork.
Boards + Sprints
4 promptsBoard Configuration
9/16✨ What it does
ChatGPT configures a Scrum or Kanban board for [team] with columns, a filter, swimlanes by epic or assignee, and card layout. Adjust the columns to how you actually work, then walk the board in tomorrow's standup.
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.
Pro tip: Default board = generic. Custom columns matching team workflow + relevant filters + swimlanes = team's tool. Investment in board = daily quality of life.
Sprint Planning Template
10/16✨ What it does
ChatGPT writes a sprint planning agenda using backlog, velocity, and capacity, with selection criteria, a capacity calculation, commitment plus stretch, and risks. Run the agenda in planning, then commit only what capacity supports.
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.
Pro tip: Bad sprint planning = chaotic sprint. Specific agenda + capacity math + risk discussion = sprint that delivers. Most teams wing it; the discipline pays.
Standup Format for Jira
11/16✨ What it does
ChatGPT designs a Jira standup: each person walks their In Progress tickets, blockers live on the tickets, and actions become tickets instead of verbal-only notes. Walk the board tomorrow, then file any blocker that is still only spoken.
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.
Pro tip: Verbal standups (yesterday/today/blockers) = forgotten. Jira-board standups (each person's tickets visible) = action items captured + blockers visible. Better signal.
Sprint Retro Format
12/16✨ What it does
ChatGPT plans a retro that uses Jira data: what shipped, what worked, what did not, and action items created as tickets. Pull the sprint report first, then write each action as a ticket before you leave the room.
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.
Pro tip: Retros without action items = same problems next sprint. Action items as Jira tickets = trackable. Vague "communicate better" = no behavior change.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Workflow + Automation
4 promptsWorkflow Design
13/16✨ What it does
ChatGPT designs a Jira workflow for [issue type] with states, transitions, validators, conditions, and post-functions. Draw it, then have a project admin add only the transitions you will actually use.
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.
Pro tip: Default Jira workflow = generic. Custom workflow matching team process + transition rules = enforces process. Most teams accept default; custom workflow = institutional.
Automation Rules
14/16✨ What it does
ChatGPT writes a Jira Automation rule for [scenario - auto-assign, transition on PR merged, notify on overdue] with trigger, conditions, and actions. Build the rule, then run a test issue through it.
Automation rule for [scenario — auto-assign, transition on PR merged, notify on overdue]. Output: trigger, conditions, actions. Jira Automation rules = no-code workflow.
Pro tip: Manual processes (assign tickets, transition, notify) = forgotten or inconsistent. Automation rules = consistent. "PR merged → ticket Done" = no human required.
Integration Strategy
15/16✨ What it does
ChatGPT plans Jira integrations with [tools - GitHub, Slack, Confluence]: PR links, channel notifications, doc links, config, data flow, and security. Connect the one tool you already live in, then verify a PR comments on the ticket.
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.
Pro tip: Standalone Jira = silo. Integrated Jira (GitHub PRs link, Slack notifications, Confluence docs) = part of stack. Integration investment = team productivity.
Jira Hygiene Practices
16/16✨ What it does
ChatGPT writes hygiene practices for [team]: stale-ticket cleanup, a protocol for tickets with no update in 30 days, honest estimates, current status, and definition-of-done enforcement. Schedule the first cleanup, then close or comment every rotting ticket.
Jira hygiene practices for [team]. Output: stale ticket cleanup cadence, rotting ticket protocol (>30 days no update), accurate estimates, current status, definition of done enforcement. Hygiene = trust in data.
Pro tip: Stale Jira data = ignored Jira data. Quarterly cleanup + active management = trust in data. "Sprint board reflects reality" = team uses it; "doesn't reflect reality" = team ignores.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides