Issue Details (XML | Word | Printable)

Key: JRA-13011
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Kai Irene Busch
Votes: 1
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
JIRA

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

Created: 03/Jul/07 09:00 AM   Updated: 06/Apr/08 07:58 PM
Component/s: Issue Fields, Sub-tasks
Affects Version/s: 3.9, 3.9.2
Fix Version/s: 3.13.x

Time Tracking:
Original Estimate: 1 week, 2 days, 4 hours
Original Estimate - 1 week, 2 days, 4 hours
Remaining Estimate: 1 week, 2 days, 4 hours
Remaining Estimate - 1 week, 2 days, 4 hours
Time Spent: Not Specified
Remaining Estimate - 1 week, 2 days, 4 hours

File Attachments: 1. Zip Archive screenshots.zip (91 kB)

Environment: Using Standalone with MSSQL as Database and JDK 1.5.0_06
Issue Links:
Duplicate
 

Participants: Anton Mazkovoi [Atlassian], Brian Feinstein, Dylan Etkin [Atlassian], Jed Wesley-Smith [Atlassian] and Kai Irene Busch
Since last comment: 28 weeks, 6 days ago
To be done by: Pair of developers
Labels:


 Description  « Hide
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



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jed Wesley-Smith [Atlassian] added a comment - 06/Dec/07 08:00 PM
The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.

Brian Feinstein added a comment - 25/Mar/08 05:14 PM
This has occurred for us as well, it was very puzzling what was going on at first!

It is a pretty serious bug since it is easy to lose subtasks in searches this way. It would be a problem especially if you had the same component name in the "moved to" project, you would not be able to notice the problem except that the id fields are different, the names would appear the same.