Release templates define the standard structure for a type of release — its checklist, approval steps, target environments, and deployment note format. When a new release is created from a template, it inherits all of these, so nothing gets skipped.
Templates are especially useful when you have different release types with different requirements — a hotfix has a much shorter checklist than a major feature release, and a template ensures each type follows the right process consistently.
| Template | When to use it |
|---|---|
| Standard Feature Release | Regular sprint-based releases with full QA, UAT, and stakeholder sign-off. |
| Hotfix Release | Fast-track deployment for critical production bugs. Minimal checklist, expedited approvals. |
| Infrastructure Release | Platform or infrastructure changes with no application code changes. Different checklist, ops team approval. |
| Internal / Beta Release | Limited release to internal users or beta group. No full QA cycle required. |
| Field | Required | Notes |
|---|---|---|
| Template Name | Yes | A descriptive name — e.g. "Standard Web Release" or "Hotfix Template". |
| Description | No | Explains when to use this template. |
| Checklist Items | No | A list of tasks that must be completed before the release can be published. Each item can be assigned to a role. |
| Default Environments | No | Pre-selects the environments that are typically used for this type of release. |
| Approval Steps | No | Named approval gates — e.g. QA Sign-off, Product Owner Approval, Change Advisory Board. |
| Notes Template | No | A pre-filled deployment notes template that appears when adding a deployment note for releases created from this template. |
The checklist is the most valuable part of a release template. Each item is a task that must be marked complete before the release can be published. Good checklist items are:
Example checklist for a standard feature release:
Approval steps are gates in the release process that require sign-off from a named role before the release can progress. Once defined in a template, they appear in every release created from it as a sequential approval chain.
To approve a step: open the release, go to the Approvals panel, and click Approve on your step. You can add a comment explaining your sign-off decision. The release can only be published once all steps are approved.
I don't see a Templates section under Releases
Release templates are configured under Project Settings → Releases → Templates. If the option isn't visible, release management may not be fully enabled for your project.
I applied a template but the checklist is empty
Templates only populate fields at the point of applying them during release creation. If you apply a template to an existing release, manually add the checklist items — they won't auto-populate on existing releases.
I want to update a template without affecting existing releases
Template changes apply only to new releases created after the change. Existing releases that were created from the template are independent copies — they are not affected by template updates.
An approval step is blocking the release from being published
Each approval step must be marked as approved by the designated approver before the release can be published. Open the release, go to the Approvals section, and ask the relevant person to approve their step.