プロジェクト

全般

プロフィール

Vote #68336

未完了

% Done for Parent Tasks [2]

Admin Redmine さんがほぼ2年前に追加. ほぼ2年前に更新.

ステータス:
Reopend
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
開始日:
2010/10/08
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
23
issue_org_id:
6609
author_id:
1329
assigned_to_id:
0
comments:
19
status_id:
8
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[Reopend]

説明

If I have parent tasks and sub tasks and I use manual (per issue) % done values, then the parent gets the average of the values of the subtasks.
However if I use the option to set % done from status updates then instead of inheriting its % done from the subtasks it takes it from the status attached on the parent task.

Example:

!parent.jpg!

In this case 3 of 4 subtasks are finished and the 4th is in progress, yet the parent task remains at 10% because its status is just 'Developing' (which means not much for a container task).

I actually have two separate requests here:

I think that parent tasks should inherit their done% from the sub tasks in both modes (note that when using per-issue Done% values I do not get the option to pick a value for the parent, it is always computed, so why not for the by-status version too?)

Rather than average the %Done of the child tasks I would prefer to weight them by the estimated time of each subtask, so if I have 2 x 8 hr tasks finished and one 4 hour task not started the parent would be at 80% and not 66%.


journals

Any news on this? I'm not able to reproduce this.

Is this one fixed already?
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Does that mean it was implemented? Which version?
--------------------------------------------------------------------------------
The behavior given by Ewan in the description is still present on source:/trunk@12577.

The implementation of the done ratio [computed] by issue status option [further referred to as 'the option'] predates the subtasking feature and its behavior has not been changed by the subtasking implementation. Such a change hasn't been discussed as part of subtasking implementation either IIRC.
Considering the scope of the option (and the fact that subtasking isn't computing issue statuses) there can be given arguments against changing the current behavior. One for example is that it would break the pattern of computing the done ratio of the issue based on its status, which is after all the main purpose of the option.

I think this definitely needs some more discussion. Especially from users who are using the option actively in production workflows.

To clarify the issue I'll attach some more screenshots:

| with done ratio by issue field | with done ratio by issue status | issue statuses config |
| {{thumbnail(rm6609-with_done_per_field.png, size=400, title=Thumbnail)}} | {{thumbnail(rm6609-with_done_per_status.png, size=400, title=Thumbnail)}} | {{thumbnail(rm6609-issue_statuses_config.png, size=150, title=Thumbnail)}} |

Refs:
* #443
* #4274
--------------------------------------------------------------------------------
@Misha: We ended up writing our own patch to fix this annoyance as part of some other improvements, but I must say it seems to negatively impact performance at times. Would be very interested in other peoples feedback.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This is a very important issue. It's not included in version 3.4.4. When will this issue be included in the new releases?
--------------------------------------------------------------------------------
I am also facing this issue in version 3.4.6. Waiting for the fix :)
--------------------------------------------------------------------------------
Looks like the calculation only works if you set the "Calculate the issue done ratio with" option to "Use the issue field" and not to "Use the issue status"

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
As alternative for 3.4.X i'm using http://redmine-search.com/redmine-issue-done-ratio-plugin, as it let me use "Use the issue field" and still change Done Ratio based on Issue Status.
--------------------------------------------------------------------------------
I'm on 4.2.3.stable and the parent percentage calculation works only with "Calculate the issue done ratio with" option to "Use the issue field".
Any feedback to fix it? thx
--------------------------------------------------------------------------------


related_issues

relates,New,22284,Issues statuses: Option to force removal of existing percentage done
duplicates,Closed,18184,Calculate parent task done ratio based on subtask status.
duplicates,Closed,13116,When setting Redmine to update the done % by status parent tasks should have the status update according to the done % of the child tasks and not the status. This is the default behavior when you just update by issue.
duplicates,Closed,15692,calculation of % done with subtickets
duplicates,Closed,23529,Calculate parent Issue's done ratio from subtasks in case of 'Use the issue status'

Admin Redmine さんがほぼ2年前に更新

  • カテゴリIssues_2 にセット
  • 対象バージョンUnplanned backlogs_23 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0