Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20313

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

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Reports
    • 3
    • 7
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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

          Form Name

            [JSWSERVER-20313] Take into Account sub-tasks when calculating the Workload by Assignee

            Such a basic hole in the time model does not get fixed. Unbelievable. Do these guys fix anything?

             

            Phil Mulholland added a comment - Such a basic hole in the time model does not get fixed. Unbelievable. Do these guys fix anything?  

            Larry added a comment -

            All these workarounds are just that, workarounds. Given that there are numerous external workarounds available, it stands to reason that internal working code could be implemented to display the data where it makes the most sense, not off to the side somewhere.

            Larry added a comment - All these workarounds are just that, workarounds. Given that there are numerous external workarounds available, it stands to reason that internal working code could be implemented to display the data where it makes the most sense, not off to the side somewhere.

            Created a very small NodeJS console application that queries all issues of a sprint (https://developer.atlassian.com/cloud/jira/software/rest/api-group-issue/#api-rest-agile-1-0-issue-issueidorkey-estimation-get).
            With that, it's quite easy to sum-up all the required estimations for each individual user. I've absolutely no idea why Atlassian has such a weird workload-calculation if it's so easy. I'm not a NodeJS professional and it took me just below an hour to create this mini-tool with just 99 lines of code (incl. calculating weeks, days, ... out of the given seconds. 

            Also still checking the workload pie gadget.... If I manually create a filter for the required sprint (to select only issues for this sprint), I can use it in the Workload Pie Chart.
            So, now I have two workarounds. 

            Alexander Christian added a comment - Created a very small NodeJS console application that queries all issues of a sprint ( https://developer.atlassian.com/cloud/jira/software/rest/api-group-issue/#api-rest-agile-1-0-issue-issueidorkey-estimation-get). With that, it's quite easy to sum-up all the required estimations for each individual user. I've absolutely no idea why Atlassian has such a weird workload-calculation if it's so easy. I'm not a NodeJS professional and it took me just below an hour to create this mini-tool with just 99 lines of code (incl. calculating weeks, days, ... out of the given seconds.  Also still checking the workload pie gadget.... If I manually create a filter for the required sprint (to select only issues for this sprint), I can use it in the Workload Pie Chart. So, now I have two workarounds. 

            Ran Lavi added a comment -

            The free workaround (not so good, but still works) is to use the Workload Pie gadget in the dashboard.

            Ran Lavi added a comment - The free workaround (not so good, but still works) is to use the Workload Pie gadget in the dashboard.

            @Ran Lavi
            Do you know of any free app to sum-up the workload?

            Alexander Christian added a comment - @Ran Lavi Do you know of any free app to sum-up the workload?

            Ran Lavi added a comment -

            Workaround (not so good, but still works) is to use the Workload Pie gadget in the dashboard.

            And of course use all kind of apps (like Structure) to sum-up correctly the workload per assignee.

            Ran Lavi added a comment - Workaround (not so good, but still works) is to use the Workload Pie gadget in the dashboard. And of course use all kind of apps (like Structure) to sum-up correctly the workload per assignee.

            Unresolved since 2017 ...

            Alexander Christian added a comment - Unresolved since 2017 ...

              Unassigned Unassigned
              acardino Anna Cardino (Inactive)
              Votes:
              41 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: