BobbinQuick answer
Jira Cloud's editor converts Markdown as you type or paste (headings, lists, code blocks, [] action items), so paste the Markdown version into the Description. On Jira Server/Data Center, which use wiki markup, paste the wiki version.
Jira Cloud (Markdown)
Atlassian's docs (checked 23 October 2026) say the editor supports Markdown in rich text fields and converts it as you go; descriptions support headings H2–H5, and [] creates an action item (used here as tick boxes).
Title: Bug: [Area]: [what goes wrong] when [trigger]
## Summary (required)
_One sentence: what breaks and who it affects._
## Environment (required)
_Version or build, URL or screen, browser or device + OS, account/plan, feature flags._
Build:
URL / screen:
Browser or device + OS:
Account / plan:
Flags:
## Steps to reproduce (required)
_Start from a known state. One action per step._
1. Logged in as
2.
3.
## Expected result (required)
_What should happen. Link the spec or last working version if you can._
## Actual result (required)
_What happens instead. Paste the exact error text._
## How often does it happen? (required)
[] Always (every try)
[] Often (more than half of tries)
[] Sometimes (less than half)
[] Once so far
## Severity (see the severity guide) (required)
_Triage may change it._
[] S1 Critical: data lost/exposed or core flow blocked, no workaround
[] S2 Major: core feature wrong or failing for a group
[] S3 Minor: works with an easy workaround
[] S4 Cosmetic: looks or reads wrong only
[] Not sure (triage will set it)
## Evidence
_Drag in a screen recording or screenshot. Add console errors, request IDs or log links._
## Console or log output
_Paste text, not screenshots of text. Remove secrets and personal data._
```
```
## Workaround
_What users can do meanwhile, or "none known"._
## Before you submit (required)
[] I searched existing issues and this is not a duplicate
[] I removed passwords, tokens and personal data from attachmentsJira Server / Data Center (wiki markup)
h2. Bug report
_Title: Bug: \[Area\]: \[what goes wrong\] when \[trigger\]_ · _Labels: bug, needs-triage_
h3. Summary (required)
_One sentence: what breaks and who it affects._
h3. Environment (required)
_Version or build, URL or screen, browser or device + OS, account/plan, feature flags._
Build:
URL / screen:
Browser or device + OS:
Account / plan:
Flags:
h3. Steps to reproduce (required)
_Start from a known state. One action per step._
# Logged in as
#
#
h3. Expected result (required)
_What should happen. Link the spec or last working version if you can._
h3. Actual result (required)
_What happens instead. Paste the exact error text._
h3. How often does it happen? (required)
* ( ) Always (every try)
* ( ) Often (more than half of tries)
* ( ) Sometimes (less than half)
* ( ) Once so far
h3. Severity (see the severity guide) (required)
_Triage may change it._
* ( ) S1 Critical: data lost/exposed or core flow blocked, no workaround
* ( ) S2 Major: core feature wrong or failing for a group
* ( ) S3 Minor: works with an easy workaround
* ( ) S4 Cosmetic: looks or reads wrong only
* ( ) Not sure (triage will set it)
h3. Evidence
_Drag in a screen recording or screenshot. Add console errors, request IDs or log links._
h3. Console or log output
_Paste text, not screenshots of text. Remove secrets and personal data._
{code}
{code}
h3. Workaround
_What users can do meanwhile, or "none known"._
h3. Before you submit (required)
* ( ) I searched existing issues and this is not a duplicate
* ( ) I removed passwords, tokens and personal data from attachmentsA filled-in example
"Checkout: card form clears after applying coupon SAVE10 (Safari 18.1, prod). Steps: 1) add any item, 2) enter card, 3) apply SAVE10. Expected: card stays filled. Actual: card fields empty, no error. 5 of 5 tries. Chrome works. Video attached."
Tips that make Jira bugs faster to fix
- Put the formula in the Summary:
[Area]: [what goes wrong] when [trigger] ([environment]). - Keep severity (effect on users) separate from Jira's Priority field (when you fix it). See the severity vs priority matrix.
- Add a screen recording to the description so the timing and state are visible.
Record the video part
Drag the MP4 into the Jira description or Attachments. Bobbin is a free Chrome extension that records your screen, a window or a tab with your microphone and an optional webcam bubble. No account, no watermark, no time limit, and nothing is uploaded: the file stays on your computer.
- Click the Bobbin icon in Chrome's toolbar and choose Record screen, window or tab.
- Pick your microphone and turn on the camera if you want the webcam bubble.
- Press Start recording, choose what to share in Chrome's picker, and wait for the 3-second countdown.
- Pause with Alt+Shift+P, stop with Alt+Shift+S, then press Download to save the file.
To keep other tabs and notifications out of it, share just the Chrome tab (the webcam bubble appears only in screen and window recordings). Bobbin saves MP4 where your browser supports it (Chrome 126 or newer), WebM otherwise, and tells you which it used.
File size: our 60-minute 1080p test came to about 246 MB (roughly 4 MB a minute) on a simple synthetic screen; busy real screens can be larger, so a 1–2 minute clip is usually small enough to attach.
From The Bug Report & QA Kit
The kit has all 10 bug templates in Jira Markdown and wiki markup. The full kit: 10 bug templates for GitHub, Jira, Linear and Markdown, 9 release checklists (126 checks), the severity guide, 8 bug-video scripts and trackers.
See the QA kit ($15, one-time) PDF + ZIP · 7-day refund · more free samples on the page
Checked on 23 October 2026 from their own pages: Atlassian Support: Markdown and keyboard shortcuts (Jira Cloud) · Atlassian Support: describe a work item. Features change; check the linked page before you rely on it.
Loom, Vidyard, Tella, Tango, Screencastify, Screenity, Zoom and Slack are trademarks of their respective owners. Bobbin is not affiliated with them. Prices and plan limits from their public pages as of 22 Oct 2026.