How to report a bug smarter? Bug template inside 🐞

How to create an effective bug report with a bug reporting template?


The answer to most of the challenges that testers and other teams that report bugs face is to implement bug reporting issue templates. 

Thanks to that, everyone inside the organization can report a bug with already prefilled descriptions and know what data should be provided in Jira issue. This way, developers gain a well-completed bug issue with relevant information. They can focus on resolution and fixing it instead of asking additional questions or even more time-consuming - trying to reproduce this bug by themselves. 

How many bug reports do testers create daily? What if we speed up the bug issue creation process by about 70%? You can save hours of their work monthly with templates.

The bug reporting template ensures that essential information, such as the steps to reproduce the bug, environment details, severity, and expected versus actual behavior, is consistently documented.

Try Issue Templates Agent for it 😊

What information should be included in a bug report template?


Summary: A concise title that summarizes the issue.

Description: A detailed description of the bug, including:

  • Steps to reproduce: Clear and specific steps to replicate the issue.
  • Expected behavior: Description of what the software should do.
  • Actual behavior: Description of what the software is doing instead.
  • Frequency: How often does the bug occur (e.g., always, occasionally, rarely)?
  • Impact: The severity and impact of the bug on the software and users.


Environment details: Information about the environment in which the bug was observed, including:

  • Operating system: Version and type (e.g., Windows 10, macOS Catalina).
  • Browser (if applicable): Version and type (e.g., Chrome, Firefox).
  • Device (if applicable): Make and model (e.g., iPhone 12, Samsung Galaxy S21).
  • Software version: The version number of the software being tested.


Attachments: Any additional files or resources that may help understand or reproduce the bug, such as screenshots, videos, or logs.

Priority: The priority level of the bug is based on its severity and impact on the software and users (e.g., low, medium, high, critical).

Assignee: The individual or team responsible for investigating and resolving the bug.

Labels/Tags: Categorization labels or tags to classify the bug (e.g., UI, functionality, performance) and make it easier to filter and search for similar issues.

Additional Notes: Any additional information or context that may be relevant to understanding or resolving the bug.

 On the Atlassian Marketplace, you can find template apps that can help you streamline your teams’ workflow and collaboration. Our app Issue Templates Agent allows users to use templates on the issue create view, further speeding up issue creation. 

Bug Report Template – feel free to copy!


Template name: Bug reporting

Summary: Bug [define issue]

Template body:





Actual results:

[Describe them here]

Expected results:

[Describe them here]


[Describe it here]


[Describe it here]

Screenshot / video

Environment details:

Software version

[insert screenshot or video]

Additional fields:

  • Priority
  • Labels 
  • Version


⭐️ You can download the free Issue Templates Cheat Sheet: Jira edition for free if you need more templates to copy. Inside: 

  • Project management templates
  • Product management templates
  • Development templates
  • Testing templates




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events