-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
6
-
Severity 2 - Major
-
4
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
It seems that project import will not remap the status IDs to the new ones when you do a project import.
Let's say that on the exported database you have New = 1, Accepted =5 and on the target system you have New = 3 and Accepted = 7 (as there is no way to force their IDs).
Project import will work but when you check the history you will see the old IDs there.
The implications on these are quite big because this will complete break all the statistics, especially the ones made by GreeenHopper : burncharts, velocity...
- relates to
-
JRACLOUD-35604 jira project import does not remap issue state changes from changeitem table
- Closed
-
JRASERVER-36105 Changing workflow did not update the issue transition in the changeitem table
- Closed
-
JRASERVER-34338 Importing individual projects from an XML backup can lead to Agile charts being wrong.
- Gathering Impact