Defect #6847
closed
Parent priorities not dropping when subtask priorities decreased.
Added by Ewan Makepeace about 14 years ago.
Updated over 11 years ago.
Resolution:
Cant reproduce
Description
I have the situation where a parent task has the highest level of priority (emergency in my system) yet none of the subtasks is at that level any more - and I cant manually change it either?
My version is Redmine 1.0.1.devel.4167 (MySQL)
This is the parent task:
These are the subtasks:
If the system was working as I expect, one or both of the mid level parent subtasks would be at emergency, but in fact none of the subtasks is, although it may have been in the past.
Files
+1 - related to #5490
The current priority handling of parent tasks does not make much sense. Also see this forum post of mine (including an example in the Redmine Demo).
If the parent task should depend on its child tasks at all (see this comment no. 13 for alternatives), I suggest to make its priority equal to the highest priority of all open sub-tasks. Same applies to start/due date and so on.
+1 - I would like to see this in combination with Andreas Bosch's proposal to let configure per parent inheritance mode.
Andreas Bosch wrote:
+1 - related to #5490
The current priority handling of parent tasks does not make much sense. Also see this forum post of mine (including an example in the Redmine Demo).
If the parent task should depend on its child tasks at all (see this comment no. 13 for alternatives), I suggest to make its priority equal to the highest priority of all open sub-tasks. Same applies to start/due date and so on.
Andreas, this whole comment is related to issue #5880 instead of this issue.
- Category set to Issues
- Status changed from New to Closed
- Resolution set to Cant reproduce
Ewan Makepeace wrote:
I have the situation where a parent task has the highest level of priority (emergency in my system) yet none of the subtasks is at that level any more - and I cant manually change it either?
Ewan, I have been trying to reproduce this defect on a current source:/trunk@7838 but haven't succeeded. I have tried several setups but at all times the parents' priority matches the highest priority of the available (open and closed, see #5880) subtasks.
Please reopen this issue if you are still able to reproduce the reported defect...
This bug is much worse reproducable with following Redmine-version:
Environment:
Redmine version 2.3.0.stable
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.13
Environment production
Database adapter MySQL
What I did:
1) Create task_1 with priority "Normal"
2) Create subtask_1 (parent = task_1) with priority "Critical"
task_1 changes its priority automatically to "Critical"
3) Create subtask_2 (parent = task_1) with priority "Low"
task_1 changes its priority automatically to "Low" though subtask_1 is still priority "Critical"
4) change priority of subtask_2 to "Normal"
task_1 changes its priority automatically to "Normal" thoubh subtask_1 is still priority "Critical"
With this bug the priority-automatisation makes less sense I think??
I cannot reproduce on Redmine 2.3.0.
Could you check priority order?
- Status changed from Closed to Reopened
- Status changed from Reopened to Needs feedback
Is the order of the priorities relevant?
I thought Redmine handles only with status_id in this case - therefore the text of the status shouldn't have any influence on the bahaviour of Redmine?
I have attached our priority-configuration ('Niedrig' = 'Low', 'Hoch' = 'High'):
So we have to reorder our priorities in the oposite way we did.
Redmine suppose that the priorities are ordered from low to high - not the opposite way.
Thank you very much! :-)
- Status changed from Needs feedback to Closed
Thank you for your feedback.
I missed the email when this was closed 1 year ago but have retested today and it is working now.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Toshi MARUYAMA 
Updated by