Defect #15742

No warning when copying subtasks to another project with different trackers

Added by Michael Heinze almost 4 years ago. Updated over 3 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution: Affected version:2.4.0

Description

Hi,

I try to describe the scenario here:

1. I have two projects, one called "Original", one called "Copy".
2. In project "Original" I activated two trackers: "Main Job" and "Job". (See original_trackers.png)
3. In project "Copy" I only activated the tracker "Main Job" - "Job" tracker is not activated. (See copy_trackers.png)
4. In project "Original" I create one issue "Main Job 1" - tracker: Main Job.
5. In project "Original" I create two Jobs "Job 1" and "Job 2" - both trackers are "Job" and their parent task is the previously created "Main Job 1". (See original_mainjob.png)
6. I copy the "Main Job 1" issue with subtasks from project "Original" to project "Copy".
7. Redmine says that the issues were successfully copied.
8. But in the "Copy" project the two issues "Job 1" and "Job 2" now have the tracker "Main Job"! (See copy_mainjob.png)

Although this behaviour is explainable (the Jobs get the tracker "Main Job" as it is the only tracker available in the "Copy" project), it would be nice if Redmine at least warned in such a case instead of saying "It's all ok".

It is getting even worse:
If you assign a custom field to the tracker "Main Job" and make this custom field REQUIRED, then Redmine does not even copy the "Job" issues, but they will be missing in the copy as the required field is not set!

copy_trackers.png (2.03 KB) Michael Heinze, 2013-12-19 13:46

copy_mainjob.png (11.5 KB) Michael Heinze, 2013-12-19 13:46

original_mainjob.png (9.51 KB) Michael Heinze, 2013-12-19 13:46

original_trackers.png (1.86 KB) Toshi MARUYAMA, 2013-12-20 03:33


Related issues

Related to Redmine - Defect #14342: Subtasks dont receive properties change when copied New
Related to Redmine - Defect #13905: Copy Subtasks does not copy subtasks into their current p... New
Related to Redmine - Defect #17068: When copying subtasks with relations between them self's ... New

History

#1 Updated by Michael Heinze almost 4 years ago

Sorry, I made a mistake: At point 8 it should be: "(See attachment 'copy_mainjob')".

#2 Updated by Toshi MARUYAMA almost 4 years ago

  • Description updated (diff)

#3 Updated by Toshi MARUYAMA almost 4 years ago

  • Description updated (diff)

#5 Updated by Toshi MARUYAMA almost 4 years ago

  • File deleted (orininal_trackers.png)

#6 Updated by Fernando Hartmann over 3 years ago

+1

#7 Updated by Toshi MARUYAMA over 3 years ago

  • Related to Defect #14342: Subtasks dont receive properties change when copied added

#8 Updated by Toshi MARUYAMA over 3 years ago

  • Related to Defect #13905: Copy Subtasks does not copy subtasks into their current project added

#9 Updated by Toshi MARUYAMA over 3 years ago

  • Related to Defect #17068: When copying subtasks with relations between them self's are lost added

Also available in: Atom PDF