Releases

Create releases for a project and group work items by the version they ship in.

A release is a named version you plan to ship, such as APP 4.0 or RMK H2, with an optional due date. Releases belong to a project. Assigning work items to a release lets you group, filter and plan by what goes out together.

Who can use it#

Permissions

release.viewrelease.manage

release.view lets you see a project’s releases. release.manage lets you create releases and move work items into or out of them. Members have both by default. Viewers can only look.

See a project’s releases#

Open the project and select Releases in the header. The Releases dialog lists each release with its name, status, description (if any) and due date, or “No date”.

Create a release#

Open Releases on the project
The create form is at the bottom of the dialog.
Enter a name
Name is required, up to 100 characters, and must be unique within the project.
Add details if you want
Description (optional) takes up to 2,000 characters, and Due (optional) takes a date.
Select Create release
The release appears in the list straight away.

Put work items in a release#

Moving work into a release is done on the board, with release swimlanes:

Open the project’s Board
Set Swimlanes to Release. Items are grouped into a lane per release, plus a lane for items with no release.
Drag a card into a release’s lane
The item is assigned to that release. Drag it into the no-release lane to take it out.

Note

A release only gets a lane once at least one item in view belongs to it. The Releases dialog and the work item page don’t have a release picker, so a brand-new release with nothing in it can’t be assigned from the board yet. The dialog’s own note that work items can’t be assigned is out of date: board swimlanes do assign them.

Using releases in views#

Table: group rows by Release to see each release’s contents with a count.
Timeline and Gantt: group by Release to see each release’s work against dates.
Board: release swimlanes, as above. + Add in a release lane creates the item already in that release.

Limitations#

Releases can’t be renamed, re-dated or deleted from the app.
A release’s status is shown in the dialog but can’t be changed there.
Releases stay with their project when the project is archived.

FAQ#

I got “A release named … already exists in this project”.

Release names are unique per project. Pick a different name. The same name can be used in another project.

Why can’t I drag a card into a release lane?

Assigning releases needs release.manage. Ask an admin to check your role.

Is a release the same as a sprint?

No. A sprint is a time-boxed batch of work your team commits to. A release is what ships. An item can be in a sprint and a release at the same time.

Still stuck? Search the docs with ⌘K, open Help inside UnitX, or contact support.