Defect #14118

When creating a subtask, the priority of the main defect might be changed unwillingly

Added by Joachim Steffenhagen about 6 years ago. Updated about 6 years ago.

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

0%

Category:Issues
Target version:-
Resolution:Duplicate Affected version:2.3.0

Description

When creating a subtask, the priority of the main defect might be changed unwillingly. Suppose the main defect has priority "Blocker" (the highest one). Now when I create a subitem for it with priority "Normal", the priority of the main defect is changed to "Normal" too.

I think this is not ideal for two reaons: First the chosen priority might not be the one you want, yet the main priority gets overwritten without any user notice (it does not even appear in the history) and therefore invalidation report data by mistake. The user should at least be queried/notified, or only "Blocker" should be chosable to the subitem.

Second it does not seem very pratical to me. This mechanism assumes that the sum of the subitems equals the whole main item which might not always be the case. You can have a main item with a high priority that has a sub item with a lower one as the sub item is only one possible part of the solution of the main one. And if that assumption that subitems constitute the main item is seen as correct by the developers, than it's questionable as to why changes to the status of the subitems don't automatically set the status of the main item. To me it seems that this is inconsistent behaviour.


Related issues

Duplicates Redmine - Feature #5875: Changes to child estimates should trigger journal entries... New 2010-07-12
Duplicates Redmine - Feature #6687: Making an issue a subtask leads to loss of issue-property... New 2010-10-18
Duplicates Redmine - Feature #5490: Option for independent subtask priority/start date/due da... Closed 2010-05-10

History

#1 Updated by Etienne Massip about 6 years ago

  • Category set to Issues

#2 Updated by Mischa The Evil about 6 years ago

Joachim Steffenhagen wrote:

When creating a subtask, the priority of the main defect might be changed unwillingly. Suppose the main defect has priority "Blocker" (the highest one). Now when I create a subitem for it with priority "Normal", the priority of the main defect is changed to "Normal" too.

Indeed. See #5875 and #6687.

Second it does not seem very pratical to me. This mechanism assumes that the sum of the subitems equals the whole main item which might not always be the case. You can have a main item with a high priority that has a sub item with a lower one as the sub item is only one possible part of the solution of the main one. And if that assumption that subitems constitute the main item is seen as correct by the developers, than it's questionable as to why changes to the status of the subitems don't automatically set the status of the main item. To me it seems that this is inconsistent behaviour.

See #5490.

#3 Updated by Mischa The Evil about 6 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Closing as duplicate.

Also available in: Atom PDF