Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-19767

Project import will break Epic report

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • 7.0.10, 7.2.15, 8.0.0, 7.12.3, 7.6.10, 8.5.0
    • Reports

      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

      1. Perform a Project import of a JIRA Software Scrum project.
      2. 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

      1. Grab the issue id and issue key of the epic you want to fix
      2. 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';
      3. Perform a project reindex.

        1. source.png
          source.png
          103 kB
        2. target.png
          target.png
          86 kB

            [JSWSERVER-19767] Project import will break Epic report

            Salvador Perez Vazquez added a comment -

            Hey, in case it is useful to someone:

            There is a necessary change in the "ID" that is set after "newvalue" and "oldvalue", since they are defined as ntext, so that value, is not an Integer and must also be in single quotes.

             

             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';

            to

            update changeitem set newvalue = '10049' where newstring = 'SSP1-53';
update changeitem set oldvalue = '10049' where oldstring = 'SSP1-53';

             

            Kind regards,
            — Salva

            Salvador Perez Vazquez added a comment - Hey, in case it is useful to someone: There is a necessary change in the "ID" that is set after "newvalue" and "oldvalue", since they are defined as ntext, so that value, is not an Integer and must also be in single quotes.    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'; to update changeitem set newvalue = '10049' where newstring = 'SSP1-53'; update changeitem set oldvalue = '10049' where oldstring = 'SSP1-53';   Kind regards, — Salva

              Unassigned Unassigned
              mmuthusamy Moga
              Affected customers:
              4 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated: