Prompt Library

ChatGPT Prompts for Jira (Tickets, Boards, JQL)

20 copy-paste prompts

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 20 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 15 prompts are free instantly — no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup · Founder, Techpresso

Last updated May 15, 2026·Hand-curated & tested by the AI Academy team

Ticket Writing

4 prompts

User Story from Idea

1/20

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.

Writes Jira user stories.

💡

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/20

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.

Writes bug reports.

💡

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/20

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

Breaks down epics.

💡

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/20

[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.

Polishes acceptance criteria.

💡

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.

Start 7-Day Free Trial

JQL Queries

4 prompts

JQL from Question

5/20

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

Writes JQL queries.

💡

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/20

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.

Builds JQL filter libraries.

💡

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/20

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

Builds Jira dashboards.

💡

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/20

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.

Plans velocity + burndown reporting.

💡

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 prompts

Board Configuration

9/20

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.

Configures Jira boards.

💡

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/20

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.

Plans sprint planning meetings.

💡

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/20

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.

Runs standups using Jira.

💡

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/20

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.

Plans Jira retros.

💡

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.

Try AI Academy Free

Workflow + Automation

4 prompts

Workflow Design

13/20

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.

Designs Jira workflows.

💡

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/20

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

Builds Jira automations.

💡

Pro tip: Manual processes (assign tickets, transition, notify) = forgotten or inconsistent. Automation rules = consistent. "PR merged → ticket Done" = no human required.

Integration Strategy

15/20

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.

Plans Jira integrations.

💡

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/20

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.

Builds Jira hygiene practices.

💡

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.

Frequently Asked Questions

Jira: enterprise standard, deepest features, customizable, complex. Linear: modern UI, opinionated, fast. Asana: cross-team coordination, less engineering-specific. Engineering teams: Jira or Linear. Mixed teams: Asana often.

Yes for first draft. AI generates from idea + context. Human refines. Generic AI tickets = low value. Personal context + AI drafting = quality + speed.

Definition of done. Most teams have implicit DoD = inconsistent. Explicit DoD = quality consistency. Codify in board column or doc; reference in retros.

Yes for power users. 30 min mastery = compounded productivity. "Show me my open tickets" = 1-line JQL vs 5-min navigator. Compound across years.

Custom workflows matching real process. Saved filters. Configured boards. Automation rules. Hygiene cadence. Default Jira = awful; configured Jira = useful. Investment matters.

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.

Start 7-Day Free Trial Explore AI for Project Managers

7-day free trial. Cancel anytime.

Browse All Prompt Collections