Feature #24198

Setting for subtasks optionally follow the project change of the parent

Added by Jérôme BATAILLE about 5 years ago. Updated over 2 years ago.

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

0%

Category:Issues
Target version:Candidate for next major release
Resolution:

Description

Hi,

When an issue is moved to another project, it's subtasks are automatically moved to the project (with no journal for the move).

This patch :
  • adds a configuration to choose if the subtasks follows
  • enable the journal for the project move on subtasks

RM_24198_Setting_for_subtasks_optionally_follow_the_project_change_of_the_parent.diff Magnifier (5.84 KB) Jérôme BATAILLE, 2016-10-28 14:34

RM_24198_Setting_for_subtasks_optionally_follow_the_project_change_of_the_parent.diff Magnifier (5.86 KB) Jérôme BATAILLE, 2016-10-28 14:56

RM_531512_Smile_Changement_de_projet_demande_-_ne_plus_faire_suivre_les_sous_taches.diff Magnifier (6.34 KB) Jérôme BATAILLE, 2019-04-02 12:18

Related issues

Duplicated by Redmine - Patch #31133: Option to forbid children issues to folow parent issue mo... Closed

History

#3 Updated by Jérôme BATAILLE almost 3 years ago

This can be surprising to see children issues moving to new parent issue project when parent is moved, because this is done without giving the choice and with no real hint.

This can be an issue when some children issues should not be seen by some members of the new project (real issue seen in our company !).

This patch adds a global option to forbid issues to follow the parent.

#5 Updated by Go MAEDA over 2 years ago

  • Target version set to Candidate for next major release

#6 Updated by Go MAEDA over 2 years ago

  • Duplicated by Patch #31133: Option to forbid children issues to folow parent issue moving to another project added

Also available in: Atom PDF