Release go / no-go approval template
For the decision before a production release. Stage 1 collects sign offs from the QA lead (no open blockers) and security (no unresolved high findings), then stage 2 needs the product owner to accept scope and the engineering manager to say go.
- App: Approval Flow for Jira
- Category: Software delivery
- Edition: Needs a paid licence (approval policies are a paid feature)
- Sign-offs: 5, 4 required, in sequential stages
Sign-offs
#| Sign-off | Required | Approvers needed | Stage |
|---|---|---|---|
| QA lead: test plan executed, no open blockers | Required | 1 | 1 |
| Security review: no unresolved high findings | Required | 1 | 1 |
| Release notes and support briefing ready | Optional | 1 | 1 |
| Product owner accepts the release scope | Required | 1 | 2 |
| Engineering manager: go for production | Required | 1 | 2 |
A stage opens only when every lower stage is signed off. Sign-offs without a stage can be given at any time.
Use it
#A Jira administrator opens Jira settings, Apps, Approval Flow settings, tab Templates, and clicks Install next to the template in the Template library section. It becomes an ordinary approval policy: apply it to a work item from the panel, or map it to an issue type. Approvers are people, so templates never contain any: assign them on the work item or with an approval rule.
Related
#- Approval Flow for Jira documentation
- Jira approval templates: all 24 templates