Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.20.10, 9.1.0
-
8.2
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
After deleting a sprint that had its capacity updated inside of a Plan, the referred Plan fails to load properly (the screen remains blank/empty).
The console logs show at least one of the following exceptions:
Nothing seems to be registered in the Jira logs.
com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:63 TypeError: Cannot read properties of undefined (reading 'find')
at com.atlassian.jpo:jpo-wr-page-simple-plans-scripts.js:5:340449
at Array.map (<anonymous>)
at wt (com.atlassian.jpo:jpo-wr-page-simple-plans-scripts.js:5:340289)
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:95125
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:94548
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:95256
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:94548
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:95224
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:94548
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:95224
com.atlassian.jpo:jpo-wr-page-simple-plans-scripts.js:5 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'find')
at com.atlassian.jpo:jpo-wr-page-simple-plans-scripts.js:5:340449
at Array.map (<anonymous>)
at wt (com.atlassian.jpo:jpo-wr-page-simple-plans-scripts.js:5:340289)
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:95125
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:94548
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:95256
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:94548
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:95224
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:94548
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5:95224
com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:39
TypeError: Cannot read property 'find' of undefined
at com.atlassian.jpo:jpo-wr-page-simple-plans-scripts.js:5
at Array.map (<anonymous>)
at Et (com.atlassian.jpo:jpo-wr-page-simple-plans-scripts.js:5)
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5
at com.atlassian.jpo:jpo-wr-page-portfolio-frontend-vendor-scripts.js:5
Steps to Reproduce
- Have a Plan based on a board.
Make sure that the Team in the Plan has the board as its Issue Source. - Create a Sprint on the above board and add at least one issue to it (either start it or don't, both ways the bug will still be reproducible).
- Back into the Plan, open the View Settings menu and Group by 'Team' or 'Sprint', and have Show capacity on timeline checked.
- Select one of the sprints in the timeline and modify its capacity.
Do not commit the changes to the Plan.
- Now go back into the board and delete the Sprint.
- Upon attempting to access the Plan again you'll be met with a blank screen.
Expected Results
The plan should load after deleting a sprint.
Actual Results
The plan does not load after deleting a sprint.
Workaround
- Access the impacted Plan.
- Now go to its configuration page by replacing '#plan/backlog' with '#settings/scheduling' directly on the URL.
- Modify the "Estimation" to another unit.
Example: From Story Points to Hours.
At this point, you can switch back to the former unit if you wish. - Select Back to Plan and the Plan should load correctly now.
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
JPO-21871 Loading...