Jira wiki markup guide
QA Repro Steps Jira Template
Format QA repro steps, environment details, evidence, and acceptance criteria as a Jira bug ticket.
Direct answer
A good Jira QA repro ticket includes summary, environment, steps to reproduce, expected result, actual result, evidence, and acceptance criteria, then uses Jira wiki markup for headings, numbered steps, inline code, and links.
Open Markdown to Jira converterWhen to use this
- A tester, support engineer, or user reported a reproducible bug.
- You need environment details and evidence in the Jira issue.
- The report includes console errors, screen recordings, or affected URLs.
Steps
- Write a one-sentence bug summary.
- Capture browser, device, app version, and environment.
- List exact numbered reproduction steps.
- Separate expected and actual behavior.
- Add evidence links and acceptance criteria.
- Convert the report to Jira wiki markup.
Example conversion
Markdown input
## QA repro ticket **Summary** Mobile Safari users cannot open the export menu. **Environment** - Device: iPhone 15 - Browser: Safari 17 - Env: production **Steps to reproduce** 1. Open /tools/resume-to-website 2. Tap Export 3. Tap Download HTML **Expected** Download menu opens. **Actual** Nothing happens and console logs `EXPORT_MENU_BLOCKED`. **Evidence** [Screen recording](https://example.com/repro)
Jira wiki output
h2. QA repro ticket
*Summary*
Mobile Safari users cannot open the export menu.
*Environment*
* Device: iPhone 15
* Browser: Safari 17
* Env: production
*Steps to reproduce*
# Open /tools/resume-to-website
# Tap Export
# Tap Download HTML
*Expected*
Download menu opens.
*Actual*
Nothing happens and console logs {{EXPORT_MENU_BLOCKED}}.
*Evidence*
[Screen recording|https://example.com/repro]Common mistakes
- Do not mix expected and actual behavior in the same paragraph.
- Do not leave environment details in screenshots only.
- Do not skip acceptance criteria after the bug is reproduced.
FAQ
- What fields should a Jira bug repro include?
- Use summary, environment, steps to reproduce, expected result, actual result, evidence, and acceptance criteria. Those sections make the bug easier to triage and verify.
- Should repro steps be numbered in Jira?
- Yes. Numbered steps are easier to follow and convert cleanly to Jira wiki ordered lists.
- Can I include console errors in a Jira bug report?
- Yes. Put short console identifiers in inline code so Jira renders them clearly, and link to longer logs or recordings as evidence.