Redmine

Hi,

after experimenting a little, I now understand that the priority (and other properties) of a parent task is determined by the priority of its sub-tasks. More specifically, the parent task's priority is always set to the highest priority of its children's priorities. This makes sense.

However, if the sub-task with the highest priority is closed, the parent task's priority should change to the highest priority of all open sub-tasks.

Example:

• Parent task
  • sub-task 1 (prio: high, status: open)
  • sub-task 2 (prio: low, status: open)
  • sub-task 3 (prio: normal, status: open)
  • sub-task 4 (prio: normal, status: open)

In this case, the parent task's priority would be "high" because this is the highest priority of all sub-tasks.

Now, "sub-task 1" has been fixed and is closed:

• Parent task
  • sub-task 1 (prio: high, status: CLOSED)
  • sub-task 2 (prio: low, status: open)
  • sub-task 3 (prio: normal, status: open)
  • sub-task 4 (prio: normal, status: open)

Now, the priority of the parent task should automatically change to "normal" because this is now the highest priority of all open sub-tasks. However, currently the priority remains at "high" although "sub-task 1" has been closed.

Am I missing something or has this already been fixed? We are using v1.0.0, but we are planning to upgrade soon anyway.

BTW: An example can be found in the Redmine demo: http://demo.redmine.org/issues/28359 - this issue has two sub-issues, one with prio "urgent" and closed, and one with prio "low" and open. The parent task's prio remains at "urgent" anyway.

Thanks!
Andreas