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 work item named for the version, with nine checklist items on it. The checklist sits on the work item the team already looks at, so the steps get done instead of living in a wiki page no one opens.
If a step belongs to someone else, such as release notes from the product manager, move it out of the checklist and into its own work item with its own assignee.
$versionTaskEach line is a checklist item on the work item. Add, remove or reorder them in the template set.
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 |
|---|---|---|
$version | The version number in the summary; a text variable you add | 28.1.0 |
$projectKey | The space key, in the description | WEB |
$version is a custom variable the app asks for. $projectKey is built in; the name comes from Jira’s older wording and works in spaces.
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.
Call the app's API from a rule.
Use this when an event in Jira, such as a field change, should start the work.
Add the app's post function to the transition that moves a release to Ready.
This works in company-managed spaces. The set is applied the moment the work item moves.
Engineering teams that ship versions on a regular rhythm and keep forgetting the same step, often release notes or the support briefing.
It suits teams where release knowledge lives with one person who is about to go on holiday.
If your release is fully automated in a pipeline, keep the steps in the pipeline and use the set only for the human steps.
For a hotfix, a shorter set with just test, deploy and tell support may fit better.
Yes. Set the Fix version on the work item, or link the work item from the version’s release page.
Add it to the template set after the release where you noticed it was missing. The next version gets it.
Yes. Our post on building a release checklist covers the steps and when to split them into work items.
Other template sets that teams use alongside this one.
Building Jira apps since 2017.