Jira Bug Report Template: Pre-Fill New Bugs With Steps to Reproduce
Short answer: Paste the template below into the Bug work type's default description. In team-managed projects that's native: Project settings > Work types > Bug > Description > default. In company-managed projects Jira has no per-issue-type description default, so use Atlassian's custom-field workaround, an Automation rule (runs after create), or an app that pre-fills the Create dialog.
The template
Summary One sentence: what is broken, where. Steps to reproduce 1. 2. 3. Expected result Actual result Environment App version / build: Browser / OS / device: Account or tenant (no passwords): Frequency Always / Sometimes / Once Evidence Screenshot, screen recording, logs or request ID
Tips: keep it short enough that people fill it in instead of deleting it; put headings, not instructions, in the body; and ask for a request ID or log line, which usually saves the first back-and-forth. In Jira's editor, make each heading line a Heading 3 (type ### and a space at the start of the line) so the template is easy to scan.
1. Team-managed projects (native)
Project settings > Work types > Bug, click the Description field and set its default text. Every new Bug opens with it; Stories and Tasks keep their own defaults. See default description templates for details.
2. Company-managed: Atlassian's custom-field workaround
Create a Paragraph custom field (for example "Bug details") with the template as its default value in a field context limited to the Bug issue type, put it on the Bug create screen, and copy it into Description with a post-function or Automation if you need it there. It works, but adds a second field and a context to maintain per issue type.
3. Automation (after creation)
Trigger Work item created, condition Work type = Bug and Description is empty, action Edit work item > Description = the template. Reporters only see the template after saving, so they rarely fill it in; better for Bugs created by email or forms than by people.
4. Also default the other Bug fields
Bugs usually need more than a description: a default Priority (see default priority per issue type), a bug-triage label or a component (see default labels and components), and maybe a default assignee for triage.
5. One app for Bug templates and defaults, per issue type
See how Default Field Values works
FAQ
Can Jira Cloud have a different description template per issue type? Team-managed projects can, in the work type settings. Company-managed projects need the custom-field workaround, Automation, or an app.
Will the template overwrite text the reporter typed? Not with the methods here: the Automation rule checks that Description is empty, and Default Field Values only fills empty fields.
Does the template apply to bugs created by email or the REST API? Automation applies to any creation channel. Default Field Values pre-fills the Create dialog and fills still-empty fields right after creation from other channels.
What should a good bug report include? Steps to reproduce, expected vs actual result, environment and evidence. Severity and frequency help triage.
Related guides
- How to Add a Default Description Template in Jira Cloud (Company-Managed and Team-Managed)
- How to Set a Default Value for a Field on Create in Jira Cloud (2026)
- How to Set a Default Priority in Jira Cloud (per Project and per Issue Type)
- All Jira Cloud guides
Disclosure: Loomwise makes the apps mentioned in the cards above and wrote this guide. Not affiliated with Atlassian. Vote counts and ticket statuses are from jira.atlassian.com as of October 2026. Last checked October 2026; Jira menus and features change, so verify in your site. Contact: hello@loomwise.app