Jira prompts
Jira holds the stories, bugs, epics and sprints that a software team lives in, and unclear tickets slow everyone down. These prompts help you turn rough notes into well-formed user stories with acceptance criteria, break epics into tasks, prepare sprint planning and refinement, write bug reports developers can reproduce, and review a backlog for gaps. Paste your own ticket text, with confidential details removed, into ChatGPT, Claude, Gemini or Copilot, then copy the result back into Jira. The prompts do not connect to your Jira site, so check fields, workflows and permissions yourself before you update real tickets.
Prompts
-
Backlog Age and Stale Issue Audit
Find old, duplicated or unclear backlog issues and decide what to close.
-
Jira Epic and Roadmap Structure Audit
Review your Jira epics for size, clear outcomes and ownership, find stalled or overlapping epics, and propose a cleaner roadmap structure.
-
Jira Acceptance Criteria and Definition of Done Audit
Score a sample of Jira stories for testable acceptance criteria and a shared definition of done, with rewrites and a team checklist.
-
Jira Bug Report Quality and Triage Audit
Audit a sample of Jira bug tickets for reproducible steps, evidence and priority consistency, and build a short bug template and triage routine.
-
Jira Dashboard and Gadget Usefulness Audit
Assess Jira dashboards and filters for stale data, unclear questions and unused gadgets, then keep the few views that drive decisions.
-
Jira Release and Fix Version Hygiene Audit
Check fix versions, release dates and unreleased issues in Jira for mismatches, orphaned tickets and release-note gaps before a release.
-
Jira Labels, Components and Naming Consistency Audit
Find duplicate, misspelled and unused Jira labels and components, and propose a naming convention and clean-up plan without bulk changes.
-
Jira Cycle Time and Blocked Work Review From an Export
Calculate cycle times, waiting times and blocked periods from a Jira export, find where work stalls, and suggest process experiments.
-
Jira Service Desk Request Queue and Response Time Audit
Audit an exported Jira service queue for response and resolution times, request categories, repeat questions and missing knowledge base articles.
-
Jira Estimation and Story Point Practice Review
Review story points, subtasks and estimate-versus-actual patterns in a Jira export to see if estimates help planning, without grading people.
-
Jira Retrospective Action Item Follow-Through Audit
Track retrospective actions in Jira across sprints to see which were completed, dropped or vague, and redesign how the team captures them.
-
Jira Permission Scheme and Project Role Review (Defensive)
Check who can create, transition, delete and administer.
-
Jira Custom Fields, Issue Types and Screens Clean-Up Audit
Find configuration clutter that slows people down.
-
Jira Sprint Health Metrics Review Without Gaming
Read burn-down, carry-over and cycle time carefully.
-
Jira Automation and Notification Noise Audit
Reduce alert fatigue and surprises.
-
Jira Backlog Health Audit From an Export
Find stale, duplicate and unready items in a backlog.
-
Jira Workflow and Status Design Audit
Check that statuses and transitions match how work really flows.
-
Jira Board and Filter Configuration Review
Check board columns, swimlanes, filters and quick filters.
-
Jira Issue Quality Audit for a Sample of Tickets
Score a sample of tickets on clarity and completeness.
-
Jira Automation Rule Safety and Value Review
Check automation rules for loops, noise and unintended changes.
-
Sprint Delivery Data Audit: Carry-Over and Scope Change
Analyse several sprints for predictability.
-
Write a Jira User Story With Given/When/Then Acceptance Criteria
Turn a rough request into a ready Jira story with testable criteria.
-
Check a Jira Story Against INVEST and Definition of Ready
Review a drafted story and return a verdict plus a rewritten version.
-
Create Jira Stories From a PRD or Requirements Document
Break a product requirements document into ordered, linked stories.
-
Split a Large Jira Epic Into Thin Vertical Stories
Slice an epic so each story delivers something usable.
-
Turn Meeting Notes Into Jira Issues With Owners
Extract actions and decisions and draft them as issues.
-
Write a Jira Bug Report From a Rough Description
Structure a vague complaint into a reproducible bug.
-
Rewrite Jira Requirements Using Agile Practice
Polish vague requirements into clear, estimable stories.
-
Draft Jira Release Notes From Resolved Issues
Convert a list of resolved issues into customer-friendly notes.
-
Sprint Review Summary From a Jira Sprint Report
Write a stakeholder summary of what was delivered.
-
Sprint Planning Agenda and Capacity Check for Jira
Plan a sprint with realistic capacity and a clear goal.
-
Sprint Retrospective Notes and Action Items for Jira
Turn retrospective input into themes and trackable actions.
-
Backlog Refinement Session Plan for a Jira Board
Run a 60-minute refinement that leaves stories ready.
-
Story Point Estimation Helper for a Jira Backlog
Compare stories to reference items and flag outliers.
-
Weekly Project Status Update From Jira Data
Write a short, honest status from exported issues.
-
Project Risk and Issue Log Built From Jira Tickets
Create a risk register from tickets and comments.
-
Definition of Done Workshop Guide for a Jira Team
Agree a definition of done and map it to the workflow.
-
Jira JQL Query Builder With Plain-English Explanations
Turn questions about work into queries you can check.
-
Jira Sprint Goal Writing and Backlog Item Selection Coaching
Craft a goal the team can believe in and test it.
-
Jira Release Readiness Checklist and Go/No-Go Summary
Create a Jira release readiness checklist and go/no-go summary to confirm a release is ready and record the decision.
-
Jira Dependency Map and Cross-Team Risk Briefing
Make dependencies visible before they cause delay.
-
Jira Epic Roadmap Summary for Stakeholders
Turn epics and dates into a clear quarterly view.
-
Jira Support Ticket to Product Backlog Item Conversion
Turn customer issues into good backlog items.
-
Update an Existing Jira Story From New Information
Merge new decisions into a story without losing its history.
-
Convert a Jira Story Into Sub-Tasks With Owners and Estimates
Break a ready story into working steps without changing its scope.
-
Write Acceptance Criteria for an Existing Jira Story
Add testable criteria to a story that has only a description.
-
Triage a Jira Bug Backlog Into Fix Now, Plan, Ask and Close
Sort a list of bugs into clear next actions with reasons.
-
Link Jira Dependencies From a List of Work Items
Turn a dependency list into correct issue links and a safe order.
-
Merge Duplicate Jira Issues Into One Clear Issue
Combine overlapping tickets without losing any information.
-
Sprint Planning Capacity Calculator and Sprint Goal Draft
Work out realistic sprint capacity and write a sprint goal the team can check.
-
Jira Bug Report Template With Reproduction Steps
Write a clear Jira bug report with summary, environment, numbered reproduction steps, expected and actual results, and evidence to attach.
-
Jira Bug Triage Checklist and Duplicate Check
Triage incoming Jira bug reports with a checklist for completeness, severity, duplicates and next owner, with a scored summary table.
-
Jira Bug Report Quality Score and Rewrite Guide
Score a Jira bug report from 1 to 5 on reproducibility, evidence and clarity, then get a rewritten version and tips to help reporters improve.
No prompts match those filters.
Frequently asked questions
Can AI write Jira user stories?
It can draft stories and acceptance criteria from your notes in a format you specify. Review them with your team and check they are testable.
Will these prompts connect to my Jira site?
No. They are text prompts; you copy results into Jira yourself.