I have some users who act as product owners as well as developers. So, they are both assigned to a parent story (in their role as Product Owner) as well as sub-tasks (as Developer). It looks like the Capacity Tracker plug-in computes the capacity / allocation at the story as well as at the sub-task level. So, it gives the impression that a particular user is overallocated for a sprint. Let me illustrate with an example. User1 is assigned to a story S1 as a product owner. The story has 5 sub-tasks, each taking 4 hours each for a total of 20 hours for the story. The 5 sub-tasks are distributed among 5 developers among which U1 is one of them. So, U1 has 4 hours worth of work to be done in the sprint. However, the capacity tracker adds the 4 hours (for the task assigned to U1) to the 20 hours for the story (which is assigned to U1) and says that they have 24 hours of work remaining in the sprint. This is obviously incorrect because a) it is counting the 4 hours for U1's task two times (once as part of the story and then as the task separately) and b) the other tasks in the story S1 are actually assigned to other users, so it should not be counted as part of U1's capacity.
Is there a flaw in my understanding of how this plugin works? if so, can this be corrected somehow to ignore the hours at the story level? All I want is for hours at the sub-task level to be included in the calculation of capacity/allocation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.