Defect #24111

Moving the parent issue from subproject to another project moves sub issues too

Added by Emanuel Reisinger almost 6 years ago. Updated almost 6 years ago.

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

0%

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

Description

If an issue with sub tasks is moved to another project (main project of the current one) the sub tasks are automatically moved to the new project, too.
Further no remark is written to the history of any of the tasks, neither to the parent nor to the sub task.

Environment:
  Redmine version                3.3.0.stable
  Ruby version                   2.1.9-p490 (2016-03-30) [i386-linux-gnu]
  Rails version                  4.2.6
  Environment                    production
  Database adapter               PostgreSQL
SCM:
  Subversion                     1.9.3
  Cvs                            1.12.13
  Git                            2.7.4
  Filesystem                     
Redmine plugins:
  redmine_agile                  1.4.0
  redmine_image_clipboard_paste  1.0.0
  redmine_mentions               0.0.1
  redmine_mylyn_connector        2.8.2.stable
  redmine_xapian                 1.6.4
  sidebar_hide                   0.0.7

History

#1 Updated by Emanuel Reisinger almost 6 years ago

An important note to the sub tasks is, that the sub tasks has to be in the same project like the main task.
The project of sub tasks which belongs to another project are not changed.

Example:

Project A
 +- Sub project B
 +- Sub project C

Main task (assigned to Sub project B)
 +- sub task 1 (assigned to Sub project B)
 +- sub task 2 (assigned to Sub project B)
 +- sub task 3 (assigned to Sub project C)

Moving Main task from Sub project B to Project A moves sub task 1 and 2 to Project A, too. Sub task 3 still remains in Sub project C. So the result looks like:

Main task (assigned to Project A)
 +- sub task 1 (assigned to Project A)
 +- sub task 2 (assigned to Project A)
 +- sub task 3 (assigned to Sub project C)

But the expected result should look like:

Main task (assigned to Project A)
 +- sub task 1 (assigned to Sub project B)
 +- sub task 2 (assigned to Sub project B)
 +- sub task 3 (assigned to Sub project C)

#2 Updated by Jean-Philippe Lang almost 6 years ago

Yes, it works like this by design but I understand that it may not be desirable to move subtasks too.
We can aither remove this behaviour (never move subtasks with parent task) or add a checkbox "Move subtasks too" when changing the project of a parent task.

#3 Updated by Emanuel Reisinger almost 6 years ago

I think it would be better to add a checkbox when moving parent task because sometimes the whole task including subtasks should be moved to another project.
When the checkbox means "Move subtasks too", then it should be not checked per default. This is the main behaviour in our usage.

Also available in: Atom PDF