New product feature process
Take each feature from idea to release the same way.
1 epic, 3 work items · On request
See the template setEach 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.
$bugTitleBugThe line under each item is a suggested scope. Write your own in each work item's description.
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.
| Variable | What it fills in | Example |
|---|---|---|
$bugTitle | The bug's summary; a text variable you add | Checkout button does nothing on Safari |
$username | The person who applied the set, in the description | Dana Ortiz |
$bugTitle is a custom variable the app asks for when you apply the set. $username is built in.
Use one way, or more than one. Each way creates the same structure.
Apply it from the app when the work starts.
The app asks for any variables, so each run carries its own details.
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.
Call the app's API from a rule.
Use this when an event in Jira, such as a field change, should start the work.
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.
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.
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.
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.
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.
Building Jira apps since 2017.