Every team that ships software has a release checklist. Freeze the branch, run the tests, update the docs, publish the notes, tell support. The checklist usually lives in a wiki page, and the release usually happens without anyone opening it.
Putting the checklist on the release work item fixes that. The steps sit where the work is, and you can see at a glance which ones are done.
Write the steps down honestly
Start from your last three releases, not from an ideal process. What did people actually do? What did they forget? A typical list:
- Freeze the release branch
- Run the release tests
- Update the version in the docs
- Write and publish the release notes
- Tell support what changed
- Tag the release
- Watch errors for a day after release
Build it as a template set
In AppsDelivered Templates, create a template set with one work item: Release $version. Add your steps as a checklist on it. If some steps belong to other people, such as release notes from the product manager, make those separate work items under it with their own assignee.
$version is a custom variable. When you apply the set, the app asks for the version number and puts it in every summary and description that uses it.
Apply it for each version
When a release is planned, apply the set and type the version. You get the release work item, its checklist and any child work items, all named for that version. Link the release work item to the Jira version so it shows up in your release view.
Improve it after each release
After each release, ask one question: did we skip or add a step? If yes, change the template set, not the work item you just closed. The next release gets the fix, and the app’s History page shows what changed and who changed it.
A checklist nobody opens is a document. A checklist on the work item is a process.



