Low Issue Summary
After upgrade from 8.5.5 to 8.16.0, when the user access the Manage Plans options, it fails when loading the page with
portfolioPlanVersion is not defined ReferenceError: portfolioPlanVersion is not defined at module.exports (https://<jira.base url>/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-manage-portfolio-scripts/com.atlassian.jpo:jpo-wr-page-manage-portfolio-scripts.js?locale=en-US:5:13380) at Object.e.Renderer.render (https://<jira.base url>/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-shared-scripts/com.atlassian.jpo:jpo-wr-page-common-shared-scripts.js?locale=en-US:5:1525) at r._renderTemplate (https://<jira.base url>/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:525:23063) at render (https://jira/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:525:22709) at constructor._renderView (https://jira/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:525:12908) at constructor.show (https://<jira.base url>/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:525:11912) at i.onShow (https://<jira.base url>/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-shared-scripts/com.atlassian.jpo:jpo-wr-page-common-shared-scripts.js?locale=en-US:27:73685) at Object._triggerMethod (https://<jira.base url>/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:525:7699) at i.triggerMethod (https://<jira.base url>/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:525:21147) at Object.s.triggerMethodOn (https://<jira.base url>m/s/32dd010021e4cc663455cd62cbcb8f8f-CDN/vexmgv/816000/1uf8w2/8.16.0/_/download/batch/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts/com.atlassian.jpo:jpo-wr-page-common-libs-only-scripts.js?locale=en-US:525:7997)
Steps to Reproduce
- Install and configure vanilla instance of Jira Software Data Center version 8.5.9.
(This is to use an old version of the AR4J App) - Create a software project with sample data.
- Install AR4J (portfolio) version 2.21.0.
- Create a classic plan.
- Update AR4J App to the latest version supported, which is 3.29.6.
- Accessing the View Plans page would show the classic plans.
- Accessing one of the classic plans would show no longer supported information with the ability to migrate the plan.
- Upgrade Jira to version 8.17.0.
(This will upgrade AR4J to the bundled version) - Try to access the View Plans page.
Expected Results
Accessing the View Plans page would show the classic plans.
Actual Results
Page is not loaded completely and it fails with the error ReferenceError: portfolioPlanVersion is not defined
Workaround
Remove the old plans and recreate using the new plan interface.
To remove the old plans:
- Identify existing plans (check all users that have previously created plans) <jira base url>/rest/roadmap/1.0/plans.json
- Run a DELETE on /rest/roadmap/1.0/plans/{id}
Note:
When preparing the list of plans for the page, a request to <jira base url>/rest/roadmap/1.0/plans.json return sa JSON with the collection and its classic Plans, however, the plans do not have an expected property called "portfolioPlanVersion", causing the script to fail.