--- title: "FAQ & Troubleshooting the App" canonical: "https://help.releasemanagement.app/space/RM4J/1081375/FAQ%20%26%20Troubleshooting%20the%20App" format: markdown --- > Macro (include) # Renaming “Releases“ to “Packages“ > ℹ️ As of **June, 2024 **we re renaming “**Releases**“ to “**Packages**“ to be aligned with our Cloud products and avoid long running confusion with “**Releases**“ in Jira. Some areas of our App will still have release notion/naming due to technical limitations, namely: > ℹ️ > ℹ️ - **API roots** will still be called */ release / *while tags and descriptions in [Swagger](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347) changed to packages > ℹ️ - **Webhook** [injectable variables](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/331710465/Automation+via+Outcoming+WebHooks#Injectable-variables-in-URL) will be called *release.** > ℹ️ - **Release notes **[injectable variables](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081356/Flexible+Release+Notes#Releasevariables) will be called *release.** > ℹ️ - **JQL functions **will still be called *[versionsOfReleases..](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1703945/Custom+JQL+functions#%E2%80%9CfixVersion-in-..%E2%80%9C-JQL-functions)** & **[issuesOfReleases..](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1703945/Custom+JQL+functions#%E2%80%9Cissue-in-..%E2%80%9C-JQL-functions-(ver.-4.1.0%2B))* # Topics > Macro (toc) --- # FAQ ## Why a version is not shown on board? 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. **Check out the Archived filter on the board. By default we do not show (and load) Archived versions to speed up board loading time. - **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. ## Why can't I delete a column or change its status? 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. ## How can I create multiple versions in several projects by a single click? Bulk version creation to be done using the **Create package **function. In order to do so: - Navigate to the "**Packages**" tab. - Click "**Create package**" 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 package**" 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 package properties. ## How can I update status of multiple versions by a single click? Release Management app has embedded functionality for massive version status changes within the scope of a package. Please read details in [Bulk status update of versions in package](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081376/Use+packages+on+board#Bulkversionactionsintherelease) chapter. ## How can I archive or unarchive multiple versions in bulk? The user can archive or unarchive multiple versions in a package. This function will be activated automatically during archive or unarchive a package. Please read more details in [Bulk version archive or unarchive operations](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081376/Use+packages+on+board#Bulkversionarchivedstatuschange) chapter. ## How can I update multiple versions start and release dates in bulk? The user is able to update start and release dates of versions in package in bulk or inherit dates from the package to the versions. This functionality is available: - On a roadmap for packages and versions with empty start and release dates. Read details in [Unscheduled panel](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081373/Roadmap+view#ScheduleversionsusingTimeline-Unscheduledpanel) chapter. - On package level. Read details in [Versions start and release dates update in package in bulk](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081376/Use+packages+on+board#Bulkversionsstart/releasedatechange) chapter. ## How the projected release date is calculated? ### **Glossary** - SD - start date - RD - release date - PRD - projected release date - PAD - projected amount of days in version/package - NDSS - Number of days since version/package started. - DPV - Done % of work in version - DPR - Done % of work in package ### **Formulas** - 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** 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 ### **Version delay status** The version is considered as delayed in two cases: 1. RD is not empty and RD is the past 2. RD is not empty and PRD is calculated and PRD > RD ### **Version delay duration** Version delay duration in days is shown if the version is delayed (see above) and RD is not empty. | | | --- | | `if(RD`    return` `(PRD!=null&&PRD>today)?(PRD-RD):(today-RD);`
`}else{`
`    return` `(PRD>RD)?(PRD-RD):0;`
`}` | ### **Package PRD** Package PRD is calculated in cases: - All versions in the package have PRD or RD (Each particular Version will have PRD or RD) - Package PRD=latest RD or PRD of all versions in the package ### **Package delay status** The package is considered as delayed in two cases: 1. Package RD is not empty and Package RD is the past 2. Package RD is not empty and Package PRD is calculated and Package PRD > Package RD ### **Package delay duration** Package delay duration in days is shown if the package is delayed (see above) and Package RD is not empty. | | | --- | | `if(Package_RD`    return` `(Package_PRD!=null && Package_PRD>today) ? (Package_PRD - Package_RD) : (today-Package_RD);`
`}`
`else{`
`    return` `(Package_PRD > Package_RD) ? (Package_PRD - Package_RD):0;`
`}` | ## How to properly upgrade version of the App? 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 [https://marketplace.atlassian.com/apps/1218705/release-management-workflows-calendar-roadmaps/version-history](https://marketplace.atlassian.com/apps/1218705/release-management-workflows-calendar-roadmaps/version-history) and plan your upgrade/downgrade strategy accordingly. # Troubleshooting the App ## How to sent us extended Debug information 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. ![image](media://21ef0d9a-b164-48dc-b77a-a7905846cccd) Go to **Network **and apply filter by **Fetch/XHR** ![image](media://032ec504-575a-477b-9fa9-689ebd03d821) **Perform the action that is causing your errors/problems** As soon as the error is shown, could you please click on the “Export HAR file“ button and share the exported file with us in the support ticket ![image-20240925-092715.png](media://dd6d0700-a52a-449d-b013-49d6fdc4de64) Appreciate it. > Macro (include)