Summary
After a Project import of a JIRA Software Scrum project, the Epic report will not be generated. The root cause of the problem is Jira is not setting correct Epic Link history items during project import.
Steps to Reproduce
- Perform a Project import of a JIRA Software Scrum project.
- Crosscheck the Epic report between the Source and Target - Target instance will not generate the Epic report graph on the page.
Expected Results
Epic report to be generated as per the Source instance.
Actual Results
The page returns a blank graph:
Workaround
- Grab the issue id and issue key of the epic you want to fix
- Execute the following queries:
update changeitem set newvalue = <EPIC ISSUE ID> where newstring = <EPIC ISSUE KEY>; update changeitem set oldvalue = <EPIC ISSUE ID> where oldstring = <EPIC ISSUE KEY>;
For example, if the epic key is SSP1-53 and the epic issue id is 10049:
update changeitem set newvalue = 10049 where newstring = 'SSP1-53'; update changeitem set oldvalue = 10049 where oldstring = 'SSP1-53';
- Perform a project reindex.
- is related to
-
JRASERVER-28748 Project Imports should include relevant Active Objects data
- Closed
-
JRASERVER-65270 Project import to allow JIRA Software Board mapping
- Gathering Interest
- mentioned in
-
Page Loading...