SupportBook a demoTry it free

Bug reporting template set for Jira

Give every bug the same three steps: reproduce it, triage it and verify the fix, each with an owner, from the moment the bug is reported.

1 bug · 3 subtasks · On request

Read: Bug triage in Jira: the same steps for every bug

Illustration of the Bug reporting process template set in the app, with sample data.

The structure

What it creates

Each run creates one Bug work item and three subtasks under it. The bug carries the title you type, and each subtask is a step every bug goes through, so nothing gets fixed before someone has reproduced it, and nothing gets closed before someone has checked the fix.

Pair the set with a bug report template on the Bug work type. The template fills in the description with steps to reproduce, the expected result and the actual result, so the person reproducing the bug starts from the same questions every time.

  • Bug: $bugTitleBug
    • Reproduce the bugFollow the steps in the report and record what happened.Subtask
    • Triage and assignSet the priority and pick who fixes it.Subtask
    • Verify the fixCheck the fix where the bug was reported, then close it.Subtask

The line under each item is a suggested scope. Write your own in each work item's description.

What fills in

Variables

Variables fill in what changes from run to run. They work in text fields, such as the summary and description. A user variable fills in a person field, such as Assignee.

Variables in the Bug reporting process template set
VariableWhat it fills inExample
$bugTitleThe bug's summary; a text variable you addCheckout button does nothing on Safari
$usernameThe person who applied the set, in the descriptionDana Ortiz

$bugTitle is a custom variable the app asks for when you apply the set. $username is built in.

When it runs

How to run it

Use one way, or more than one. Each way creates the same structure.

  1. 01

    On request

    Apply it from the app when the work starts.

    The app asks for any variables, so each run carries its own details.

  2. 02

    From a workflow transition

    Add the app's post function to the transition to Confirmed on your bug workflow.

    This works in company-managed spaces. The set is applied the moment the work item moves.

  3. 03

    From Jira Automation

    Call the app's API from a rule.

    Use this when an event in Jira, such as a field change, should start the work.

Who it's for

Engineering and QA teams that get bugs from many places: support, testers, customers and the team itself.

It suits teams where bugs get fixed but not verified, or where the same bug comes back because no one checked the fix.

When not to use it

If a bug tracking tool outside Jira is your system of record, keep the steps there and link the Jira work item to it.

For a quick fix with no customer impact, the three subtasks may be more process than the bug needs. Use them for bugs that reach users.

Bug reporting process: common questions

Can the subtasks go to different people?

Yes. Set an Assignee on each subtask in the template set, or add a user variable so the app asks who should get each step.

Does this replace the Create dialog?

No. People still report bugs in Jira's Create dialog, where a bug report template fills in the description. The template set adds the steps that come after.

Can we add a step for regression tests?

Yes. Add a subtask to the template set, and every bug from then on gets it. Edit the set, not the work items it already created.

Other template sets that teams use alongside this one.

Browse the template library
$featureName
Write the spec
Build and test
Release and announce
ExampleProduct

Take each feature from idea to release the same way.

1 epic, 3 work items · On request

See the template set
Release $version
Freeze the release branch
Run the release tests
Update the version in the docs
+6 more
GuideEngineering

Your release steps as a checklist, ready for each version.

1 work item, 9 checklist items · On request

See the template set
Sprint $sprint kickoff
Confirm sprint scope
Update the board filters
Book the sprint review
+1 more
GuideEngineering

The kickoff epic and its work items, ready to apply at the start of each sprint.

1 epic, 4 work items, 1 subtask · On request

See the template set
Part of AppsDelivered

Repeatable work, delivered.

Building Jira apps since 2017.

AppsDelivered CommentsReuse your team's replies.See AppsDelivered CommentsAppsDelivered FeedsTurn new posts into work items.See AppsDelivered Feeds