Details
-
Bug
-
Resolution: Fixed
-
High
-
3.9, 3.9.2
-
Using Standalone with MSSQL as Database and JDK 1.5.0_06
-
3.09
-
Description
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
Attachments
Issue Links
- is duplicated by
-
JRASERVER-11298 Move issue from one project to another results in JIRA displaying two identical versions, post move. One for tasks and another for sub-tasks.
- Closed
-
JRASERVER-14754 Moving an issue with sub-tasks to another project causes the sub-task's Version to appear in the destination project.
- Closed
- is related to
-
JRASERVER-16007 Fix version is not modified after a move depending on permissions
- Closed
- relates to
-
JRASERVER-17312 The "Move" operation may produce subtasks with invalid empty values in target project
- Closed