Manual TestingPublished: 7 min read
JIRA Bug Report Template — Copy-Paste with Real Examples
JIRA-ready bug report template with markdown, severity, priority, environment, and steps. Includes 3 fully-written example bugs.
Avinash Kamble
Founder & QA Engineer at SoftwareTestPilot
2026-07-17 · By Avinash Kamble, reviewed by Priyanka G.
Paste this into every JIRA bug and your team will thank you.
The template (markdown)
*Environment*
Build: v2026.7.2
OS: iOS 18.2 / Android 14 / Windows 11
Browser/App: Firefox 128 mobile
User: [role]
*Preconditions*
- [feature flag / seed data / user state]
*Steps to reproduce*
1.
2.
3.
*Expected result*
*Actual result*
*Severity*: Critical / High / Medium / Low
*Priority*: P0 / P1 / P2 / P3
*Reproducibility*: Always / Intermittent (X/Y)
*Attachments*: screenshot, HAR, video, logsExample 1 — checkout crash
*Title*: Checkout — 3DS iframe closes after 5s on Firefox 128 mobile
Steps: 1) Add SKU-42, 2) checkout, 3) card 4000-0000-0000-3220
Expected: challenge stays until submission
Actual: iframe closes; order fails with PSP_TIMEOUT
Severity: High · Priority: P1 · Reproducibility: AlwaysExample 2 — data loss
*Title*: Account deletion also deletes shared team projects
Steps: 1) User A owns team T with User B, 2) A deletes account
Expected: team survives, ownership transfers to B
Actual: team T is hard-deleted; B loses all data
Severity: Critical · Priority: P0 · Reproducibility: AlwaysExample 3 — cosmetic
*Title*: Footer link "Privacy" underlined only on hover
Severity: Low · Priority: P3Auto-fill the template
Describe the bug in a sentence in the AI Bug Report Writer and it emits this exact JIRA-ready markdown.
Frequently asked questions
1.Should I use JIRA's built-in fields or markdown?
Use custom fields for severity/priority (searchable) and markdown for the narrative sections.
2.How long should a bug title be?
60–90 chars. Action + result + context. No 'BUG:' prefix (JIRA already knows).
3.Do I need to attach logs to every bug?
For backend/API bugs yes. For UI-only cosmetic bugs, a screenshot is enough.
4.Can I template this at the JIRA project level?
Yes — set a default description in the issue-type screen so every new bug starts with these headings.
Keep going
Practice these questions
Run a live QA mock interview tailored to this topic and get per-skill scoring in minutes.
Was this article helpful?
Cluster · Manual Testing
More from Manual Testing Basics
Test types, defect lifecycle, exploratory testing.
More in this cluster
- Career & Interview PrepThe Honest Truth About Manual Testing Salaries in 2026 (Real Data)
- Manual TestingTest Pyramid Explained: A Practical Guide for QA (2026)
- Manual TestingHow to Write Test Cases for a Login Page (with Examples)
From the Manual Testing pillar
Keep building your QA edge
Pillar guides- AI Mock Interviewpractice these questions with our AI mock interviewLive AI-powered mock interviews with rubric feedback.
- ATS Resume ReviewSoftwareTestPilot's ATS resume checkerFree AI ATS scoring with rewrite suggestions.
- QA Jobs Radarsee today's openingsLive QA / SDET / automation job feed, refreshed daily.
Continue reading
Join the QA Community
Connect with fellow testers, share job leads, and get career advice.
Premium QA Resources
Stop Reinventing the Wheel. Upgrade Your QA Arsenal.
Take your testing skills from beginner to Lead Engineer. Supercharge your daily workflow with our premium digital resources.
- Ready-to-use testing strategy templates
- Advanced API & UI automation guides
- ⏱️ Save 10+ hours a week on test planning


