ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

fix incorrect auto-update algorithm used in % complete for an issue with subtasks (Feature #603)


Added by Crazy Gir at 2011-09-01 07:25 pm.


Status:Open Start date:2011-09-01
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:Issue tracking
Target version:-
Remote issue URL: Affected version:

Description

If an issue has subtasks, the parent's % complete is automatically updated/calculated based on the number of issues closed/not-closed. this is a bit silly, as it is often flat out wrong for the situation the issue describes.

as an example: if you are working on an issue and find a something that ought to be a subtask, you create it and work through that task. Once complete, if when you close the issue, the parent issue has its percent complete updated. if you have one subtask, the percent complete is updated to 100% but you may have other work to do on the issue, or even new subtasks to create, which doesn't really match 100% complete.

I believe this would be ok if the logic were a little different (in choosing the percentage), but at the very least, an admin/manager should be able to update/edit this value. currently, in a situation like the above, the end result is we get incorrect information in the issue, creating cruft that can't be removed, and requiring additional cruft to clarify/comment on. this is the sort of thing that would be incredibly helpful when functioning in line with your flow, but when it doesn't it is more of a burden and annoyance.


History

Also available in: Atom PDF