Defect #18068

Copying Projects & Parent Child Issues

Added by James H almost 5 years ago. Updated over 4 years ago.

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

0%

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

Description

Issues that have parent child relationships only show up as nested in a tree view in the issues list when the issues are in order (parent first then children immediately below it).

When copying projects...
  • If I have the issues in order to show up in a nested view, the parent issue still gets copied first before its children and shows up incorrect.
  • If I put the issues in opposite order, it still behaves similarly.
  • I have no way to have a nested view of issues after copying a project.

i.e.
Project Issues to be copied:
- Child Issue 1.1
- Child Issue 1.2
- Child Issue 1.3
Parent Issue 1
Parent Issue 2
- Child Issue 2.1
- Child Issue 2.2
Parent Issue 3
- Child Issue 2.1
- Child Issue 2.2

becomes:
- Child Issue 1.1
- Child Issue 1.2
- Child Issue 1.3
Parent Issue 1
- Child Issue 2.1
- Child Issue 2.2
Parent Issue 2
- Child Issue 2.1
- Child Issue 2.2
Parent Issue 3

copy_source.png (35.4 KB) Toshi MARUYAMA, 2014-11-08 12:08

copy_result.png (36.9 KB) Toshi MARUYAMA, 2014-11-08 12:08

History

#1 Updated by Toshi MARUYAMA over 4 years ago

  • Related to Feature #7907: Display Issues in a hierarchy (tree) added

#2 Updated by Toshi MARUYAMA over 4 years ago

  • Related to deleted (Feature #7907: Display Issues in a hierarchy (tree))

#3 Updated by Toshi MARUYAMA over 4 years ago

source:tags/2.4.7/app/models/project.rb#L852 says "parent issues get copied before their children".
If you want to see issue as tree, you need to sort by id or parent issue.
For more details, see #7907.

Copy source:

Copy result:

Also available in: Atom PDF