Release a version
Mark a release as published, request the approved change if your desk requires it and notify the related service tickets.
On this page
Releasing a version means recording that it went to production. Its done items move to Released and the service tickets that were waiting for that solution get the notification. If your desk requires an approved change to go to production, releasing first requests that change.
Before you start
You must be the desk's Lead.
The release must be Planned or In progress.
Check that its items are in Done. Releasing doesn't require it, but only items in Done move to Released; the rest stay where they are.
If the desk requires an approved change, you need access to the service desk where the change is created. See Definition of done and release to production.
Release when the desk doesn't require a change
Go to Versions and press Release on the release's row, or open it and press Release at the top.
The window reminds you if there are unfinished items, for example There are 2 unfinished items in this release., and that the linked service tickets will be notified.
Press Release.
The release moves to Released, with today's date.
Release when the desk requires an approved change
Press Release on the release.
The window says that a change will be created in the service desk and that the release will wait for CAB approval.
Press Request the change.
You see the notice The change … was requested with its number. The release stays Waiting for the change and its details show Linked change: with the change's number and status, and the sentence The release goes out once the CAB approves it.
The change is created with the type the lead defined (Standard or Normal) and with the list of the release's items. While the release is waiting, the Release button doesn't appear.
If the CAB rejects the change, the release goes back to In progress. Pressing Release again requests a new change.
To follow the change, click its number. See Problems and changes.
What happens after releasing
The release's items that were in Done move to Released.
Each service desk ticket linked to those items gets a note saying the item was released in the version. That way the agent knows they can notify the requester. See Escalate a ticket to development.
The release no longer appears in the Release field of item pages: items can no longer be assigned to it.
A released version can no longer be edited or archived from the list.