There are several reasons why a version is not shown on a board:
A user does not have"Browse project" permissions. In this case, no versions of this project will be shown on the board.
The version has been archived. In this version of the Release Management app, it is not possible to see archived versions. This feature will be added in future versions.
The project has been deleted from the board configuration. In cases where the project has been removed from the "Projects in the board" section, all versions will correspondingly disappear.
Usually, it is not possible to delete a column for two reasons:
The column contains versions. A column with versions inside cannot be deleted. Also, the status of such a column cannot be changed. In order to delete such a column - or change its status - please move the versions to other columns and perform the operation again. Also, it is valid if hidden versions are inside the column. In this case the icon will be shown next to versions count in the table.
The column is Default. It is not possible to delete or change the status of default columns.
Bulk version creation to be done using the Create release function. In order to do so:
Navigate to the "Releases" tab.
Click "Create release" button.
Select projects where you want to create versions in
In corresponding projects, type the new version names you want to create.
You can create as many versions as you like for each project.
Click "Create release" button. A confirmation dialog will pop up. After clicking the confirmation button all the versions will be created in the corresponding projects.
Start and Release dates of the new version should be taken from the release properties.
Release Management app has embedded functionality for massive version status changes within the scope of a release. Please read details in Bulk status update of versions in release chapter.
The user can archive or unarchive multiple versions in a release. This function will be activated automatically during archive or unarchive a release. Please read more details in Bulk version archive or unarchive operations chapter.
The user is able to update start and release dates of versions in release in bulk or inherit dates from the release to the versions. This functionality is available:
On a roadmap for releases and versions with empty start and release dates. Read details in Unscheduled panel chapter.
On release level. Read details in Versions start and release dates update in release in bulk chapter.
SD - start date
RD - release date
PRD - projected release date
PAD - projected amount of days in version/release
NDSS - Number of days since version/release started.
DPV - Done % of work in version
DPR - Done % of work in release
PRD = SD + PAD;
PAD = (NDSS*100)/DP;
NDSS = today-SD (in days)
DPV = (done_issues_in_version+in_progress_issues_in_version/2)/all_statutes_issues_in_version*100
DPR = (done_issues_in_all_versions+in_progress_issues_in_all_versions/2)/all_statutes_issues_in_all_versions*100
Version PRD is calculated when all conditions below are met:
SD is not empty
SD is in the past
% of done work >=30%
version is unarchived
version is unreleased
The version is considered as delayed in two cases:
RD is not empty and RD is the past
RD is not empty and PRD is calculated and PRD > RD
Version delay duration in days is shown if the version is delayed (see above) and RD is not empty.
|
Release PRD is calculated in cases:
All versions in the release have PRD or RD (Each particular Version will have PRD or RD)
Release PRD=latest RD or PRD of all versions in the release
The release is considered as delayed in two cases:
Release RD is not empty and Release RD is the past
Release RD is not empty and Release PRD is calculated and Release PRD > Release RD
Release delay duration in days is shown if the release is delayed (see above) and Release RD is not empty.
|
Server and Datacenter versions on Release Management App is a downloadable versions running on client hosting environment and connected to local database. Therefore it’s important to follow a prescriptive procedure for upgrading versions, namely
It’s a recommended approach to upgrade versions of the App 1-by-1 and do not jump between versions. This is the only proper way to insure integrity of your local database so all the alter- and migration- sprints will be applied properly. In case you jump to higher versions by skipping some in the middle there’s a chance that some of the Release Board data won’t be consistent and board could not load properly. |
You can always check the latest list of available versions at Atlassian Marketplace
and plan your upgrade/downgrade strategy accordingly.
Sometimes the problem is not obvious and we need an extended Debug information to troubleshoot. Therefore, please follow the below guide to collect and send us such details so our team resolve your particular issue faster.
Right mouse click at some free space off the App and choose Inspect menu item. This will open your bowser development console.
Go to Network and apply filter by Fetch/XHR
Perform the action that is causing your errors/problems
As soon as the error will be shown, could you please check if any red lines will be in the following table?
If Yes, for each read line could you please send the following information to our team
Content from Headers tab. Just Copy & Paste it in support ticket.
Content from Response tab. Just Copy & Paste it in support ticket.
Appreciate it.