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

Component of a subtask is still component of original project after moving an issue

XMLWordPrintable

      Hi,

      I did the following:

      I cloned an issue including its subtasks in project A. The clone and each subtask has assigned component "PLC" in project A. Then I moved the clone with its subtask to project B. During the moving process I was told that step 2 is not necessary: components unknown ( because there are no components yet in project B, its completely empty). After finishing the moving process I had a look into the project overview.
      There were now 7 open issues assigned to component "PLC" and one issue without an assigned component.

      I then went to the administration overview. There was still no component available/created.

      (After creating a new component "PLC" for project B I had two entries "PLC" on the project overview on the tab open issues....)

      Reindexing didn't help. I could reproduce it n-fold.

      My opinion:
      I believe that the subtasks have still the component of the original project A assigned. I had a look into the database and it was like this. The issue in project B was still linked to the component in project A.

      Solution: Either I should be asked what component should be assigned to the subtasks (as for the main issue) or no component should be assigned?!?!

      Hope you can follow.

      Cheers, Irene

              bbain bain
              86ba69e984ed Kai Busch
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 60h
                  60h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 9h Time Not Required
                  9h