Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-35604

jira project import does not remap issue state changes from changeitem table

    XMLWordPrintable

Details

    Description

      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...

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-35604 jira project import does not remap issue state changes from changeitem table

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-36105 Changing workflow did not update the issue transition in the changeitem table

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-34338 Importing individual projects from an XML backup can lead to Agile charts being wrong.

          • Low - Low priority issues
          • Gathering Impact

          Activity

            People

              Unassigned Unassigned
              73f0b2e75f82 Sorin Sbarnea (Citrix)
              Votes:
              9 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: