explore all "Fix Versions" from projects added to a board
add/remove "Virtual Versions" via custom JQL or Epic Link (available in App ver. 4.0+)
group versions by releases
view version details
change status of any version using drag-and-drop
search versions by name
search versions by Archived status
organize versions order in the column using drag-and-drop
Versions are displayed as cards with the following information:
release date and delay status
project details (icon and key) for "Fix Versions"
version issues progress statistics
Type of versions
Available in App ver. 4.0+
Release Management App is built around 2 type of versions, namely
Fix Versions - standard versions reside in the projects (also called as Jira Releases)
Virtual Versions - the versions that are proprietary to Release Management App only and could be
Throughout this section and the rest of documentation when we use a notion of “version“ both Fix Version and Virtual Version. In case, there are limitations or difference in use cases an appropriate notice will be made.
You can create new versions directly from the board, without the need to navigate between projects, and use the built-in create version function.
Click "Create version" button to open a new version dialog:
Project - select a project to create a version in. Only the board projects where the current user "Create version" permissions are displayed.
Name- version name is the only mandatory field.
Description, Start date, Release date are optional version fields.
Click the "Save" button to create a new version which is added to the bottom of the default unreleased board column.
Available in App ver. 4.0+
Click “Create > Create virtual version“ to open new version dialog:
By default the version is JQL-based and you need to specify a valid JQL that will be executed by your Jira Instance.
If you want to derive the version from Epic toggle the Epic trigger and specify existing Epic Key.
The rest of the fields are the same as fixVersion.
If you click a version card on the board the version dialog is displayed with the active Summary tab by default.
You can view and update the following version fields using inline editing:
In addition to version properties the following additional information about version is available:
projected release date
For Virtual Versions summary includes the information about custom JQL or Epic key used that could be also edited.
Issues statistics is a progress widget which shows the number of version issues grouped by issue status category: To Do, In Progress, Done
The versions on the board can be filtered by Archived property:
In situations where archived and unarchived version are shown on the board, archived releases will be "greyed" and an “Archived” label will be shown on the card. Archived versions may be moved to another column or edited without any restrictions.
A user can delete a version from the board. In order to do so, right click on the version and choose "Delete" option:
Group versions by release
You can group versions by releases using Release Swimlanes toggle.
If the same version is added to several releases and release swimlanes are enabled then it will be displayed in every release swimlane.
When such a version is moved to another column in one swimlane it will be automatically moved to the same column in all other swimlanes.
Sync-up version and release dates
When releases contain a large number of versions would be difficult to:
keep versions and release dates in a consistent state
ensure each version has a start date that is equal or later than the start date of the release
ensure the version release date is earlier than, or equal to, the release date of the release
Release Management app automatically checks the abovementioned conditions and suggests to update the release to keep its dates in a consistent state with versions.
In theUpdate versiondialog user can:
update release with the suggested dates
keep original dates and accept inconsistency
cancel an operation.
TheUpdate versiondialog is displayed in the following cases:
To ensure consistency:
If the release date of the release is not empty and the nested version has a release date later than the release date of the main release
If the start date of the release is not empty and the start date of the nested version of the release is earlier than the release start date
To schedule release, if it has empty start or release dates
If the start date of the release is empty and the nested version of the release has a start date. In that case the app will suggest initiating release start date with the version start date.
If the release date of the release is empty and the nested version of the release has the release date. In that case the app will suggest initiating a release date of the release, using the version release date.