-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
8
-
Many organizations would like to work with remaining estimations at the sub-task level.
The workload by assignee window at the title of the sprint doesn't take into account a (very common) situation where the story has several sub-tasks, each one assigned on a different assignee.
For that case, the workload by assignee is totally wrong and doesn't enable easy planning of the sprint. Workaround is to use all kind of dashboard gadgets to calculate the total remaining estimation at the sub-task level, but this is not a very good workaround, since it is separate from the backlog view of the board.
Example:
- Story A, original estimate 20h, remaining estimate 0h, Assigned on User A
- Sub-task A1, original estimate 10h, remaining estimate 12h, assigned on user A
- Sub-task A2, original estimate 10h, remaining estimate 15h, assigned on user B
Expected result:
when viewing the workload by assignee, it should show:
- User A: Original estimate: 20h, remaining estimate 12h (original estimate should be calculated only from the stories, not the sub-tasks)
- User B: Original estimate: 0h, remaining estimate 15h (original estimate should be calculated only from the stories, not the sub-tasks)
Actual result:
when viewing the workload by assignee, it shows: (takes into account only stories, not sub-tasks)
- User A: Original estimate: 20h, remaining estimate 0h
- User B: Original estimate: 0h, remaining estimate 0h
- is cloned from
-
JSWCLOUD-15991 Take into Account sub-tasks when calculating the Workload by Assignee
- Future Consideration
- is related to
-
JSWCLOUD-16166 The Workload by Assignee shows the remaining time for subtasks as a sum in the parent task instead of to the assignee
- Closed
- relates to
-
JSWCLOUD-11177 Ability to see 'Remaining Estimate' in 'Workload by Assignee' summary
- Closed