Releases
Group the items that go to production together, follow their progress, draft the release notes and release them.
A release groups the items that go to production together, for example 2.4.0. It helps you know what's left for the next delivery, draft the release notes and notify customers who reported a problem when the solution is already published. Releases exist in Scrum and Kanban desks.
To see them, go to Desks, choose the desk and press Versions.
What it looks like
The table shows, for each release:
Release: its name. Click to open its details.
Status: see the table below.
Target date, or the date it was released.
Items: done against the total, with a progress bar.
Change: the number of the linked change and its status, if the desk requires one to go to production.
Releases in progress appear first, then those waiting for their change, the planned ones and the released ones.
Release statuses
Status | What it means |
|---|---|
Planned | Created, with items to do |
In progress | The team is working on its items |
Waiting for the change | Its release was requested and it is waiting for the CAB to approve the change in the service desk |
Released | It went to production |
Archived | It is no longer shown among the active ones. Its items don't change |
Archived releases don't appear in the list. To see them, press Show archived at the end of the table (the number in parentheses says how many there are); Hide archived hides them again.
Who does what
The Lead creates, edits, archives and releases versions, and asks Elion for the notes.
Members and QA assign items to a release from each item's page.
Everyone who sees the desk can open the releases and read their notes.