Change approval (CAB, normal change) template
For change managers sending a normal change to the change advisory board. Stage 1 needs the change owner and a technical peer reviewer, then stage 2 needs the service owner and two CAB members, with user communication as an optional step.
- App: Approval Flow for Jira
- Category: IT operations
- 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 |
|---|---|---|---|
| Change owner confirms scope, risk rating and rollback plan | Required | 1 | 1 |
| Technical peer review of the implementation steps | Required | 1 | 1 |
| Service owner accepts the impact and the maintenance window | Required | 1 | 2 |
| CAB approval (2 members) | Required | 2 | 2 |
| Communication to affected users is prepared | Optional | 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