Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-15991

Take into Account sub-tasks when calculating the Workload by Assignee

XMLWordPrintable

    • 54
    • 24
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian status as of November 2023

      Hey everyone,

      Thanks so much for your feedback. Our team is currently working on this and we expect to be rolled by the end of the calendar year. The design we have at the moment should allow for you to see workload by assignee include subtasks or exclude subtasks - you'll be able to toggle it. 

      If you're interested in giving more feedback or chatting about anything related to finding your work, reach out to me at https://calendly.com/april-atlassian/jsw?month=2023-11. I'm also happy to run through designs with you if possible to get early feedback.

      Regards,

      April

       

      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:
      On a board which is using the Estimation Statistic of "Original Time Estimate" and the Time Tracking option of "Remaining Estimate and Time Spent":

      • 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 27h
      • User B: Original estimate: 0h, remaining estimate 0h

              4b7910ae10b4 April Chi
              90d124564953 Ran Lavi
              Votes:
              377 Vote for this issue
              Watchers:
              183 Start watching this issue

                Created:
                Updated: