-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Issue Summary
When the user creates the new scenario, ARJ copies the scenario release info into the new scenario. However, the issue's release is not updated in the new scenario. When the user try to bulk edit the releases an error will be displayed.
Steps to Reproduce
- User create releaseX in the scenarioA, and assign the releaseX to issueX
- Create scenarioB based on ScenarioA
- Switch to scenarioB and try to select the issueX and then select bulk edit release.
Expected Results
A window will pop up to set the new release.
Actual Results
The error message: "Something's gone wrong" is displayed and you can't set the release for these issues.
The below frontend exception is thrown in the xxxxxxx.log file:
Stack Trace Cannot read properties of undefined (reading 'name') TypeError: Cannot read properties of undefined (reading 'name') at https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/async-plan-timeline.e5a83dbf.js:839:429512 at Array.map (<anonymous>) at u.getCurrentValue (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/async-plan-timeline.e5a83dbf.js:839:429500) at u.render (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/async-plan-timeline.e5a83dbf.js:839:429178) at i5 (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:107548) at i6 (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:107326) at c (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:145828) at so (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:133115) at https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:129878 at a6 (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:129886) at https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:82751 at y (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:161674) at oh (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:82457) at oy (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:82697) at om (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:82632) at G (https://jira-frontend-bifrost.prod-east.frontend.public.atl-paas.net/assets/shared~vendor~ar.b7458199.js:3:155089)
Workaround
You need to update the issues individually.
