Project

General

Profile

Actions

Feature #24198

open

Setting for subtasks optionally follow the project change of the parent

Added by Jérôme BATAILLE over 7 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Start date:
Due date:
% Done:

0%

Estimated time:
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

Files


Related issues

Has duplicate Redmine - Patch #31133: Option to forbid children issues to folow parent issue moving to another projectClosed

Actions
Actions #3

Updated by Jérôme BATAILLE almost 5 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.

Actions #5

Updated by Go MAEDA almost 5 years ago

  • Target version set to Candidate for next major release
Actions #6

Updated by Go MAEDA almost 5 years ago

  • Has duplicate Patch #31133: Option to forbid children issues to folow parent issue moving to another project added
Actions

Also available in: Atom PDF