Versioning and release
Your release steps as a checklist, ready for each version.
1 work item, 9 checklist items · On request
See the template setEach run creates an epic named for the feature and three work items under it: the spec, the build and the release. Product, engineering and marketing each own their part, and the epic shows where the feature stands.
Many teams create the epic during planning and add the work later. Since version 27.0.0 you can apply the set under an epic that already exists, so the work items join the epic your planning tool created.
$featureNameEpicThe 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 |
|---|---|---|
$featureName | The epic's summary; a text variable you add | Saved filters on mobile |
$parentSummary | The epic's name, inside each work item's description | Saved filters on mobile |
$featureName is a custom variable the app asks for. $parentSummary is built in and fills in from the parent work item.
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.
Pick the epic when you apply the set.
The set adds only its work items under the epic you picked.
Call the app's API from a rule.
Use this when an event in Jira, such as a field change, should start the work.
Product managers who run several features at once and want each one to follow the same path from spec to launch.
It suits teams where launches go out without release notes, or where support hears about a feature from customers first.
For a large initiative with many teams, one epic per feature may be too small. Use it for the features inside the initiative instead.
If your spec lives in a product tool, keep it there and link it from the Write the spec work item.
Yes. Add a work item for design to the template set, between the spec and the build, and give it to your designer.
The product manager for the feature. Each work item under it goes to the person who does that stage, so the epic shows who is working on what.
Yes. Add as many work items or subtasks as your feature work needs. The set creates all of them each time.
Other template sets that teams use alongside this one.
Building Jira apps since 2017.