Workload by Assignee - {sprint name} Remaining Time Estimate, where does this data come from?

[Buck Forst]

Before I start sprint, I see that there is a Workload by assignee option to review associated with the active or backlog sprint bucket but this column isn't clear where the data is coming from.  Here is the column I'm referring to:

But if I run a query on a specific user, the stories or sub-tasks assigned to that individual does not equal the time listed in the Remaining time estimate column.  

Can anyone school me on what I'm missing?

[Divya Sharma]

@Buck Forst  Could you let me know what query you ran on the user for the remaining estimates in a sprint?

[Mary from Planyway]

Hi @Buck Forst 

It's Mary from Planyway for Jira: workload, roadmap, time tracking

The "Workload by assignee" option in Jira, associated with the active or backlog sprint bucket, is designed to help you understand how work is distributed among team members for a particular sprint. This feature shows the remaining work (usually in terms of time) that is assigned to each member, allowing you to balance the workload more effectively. However, discrepancies between the "Workload by assignee" data and the actual issues assigned to an individual can arise due to several factors:

1. Time Estimation Configuration: Ensure that your project's time tracking and estimation settings are configured consistently. Jira allows for time estimation using either "Original Time Estimate" or "Remaining Time Estimate," and your project could be using one or a mix of both. If the team updates only one of these fields, it could lead to discrepancies.

2. Sub-tasks and Parent Issues: Sometimes, time estimates are provided at the sub-task level but not rolled up to the parent issue, or vice versa. Depending on how the "Workload by assignee" calculates the total (whether it includes sub-tasks, parent issues, or both), there might be differences if you're only looking at stories or sub-tasks for an individual.

3. Issue Status: The "Workload by assignee" might be including issues across different statuses (e.g., To Do, In Progress, Done) in its calculation. If your query filters out issues based on their status (e.g., only looking at "In Progress" issues), this could lead to discrepancies.

4. Filters Applied in the Query: Check if the query you're running to list the stories or sub-tasks assigned to an individual includes the same criteria as the "Workload by assignee" calculation. It's possible that the query might be filtering out certain issues (e.g., by project, issue type, or status) that are included in the "Workload by assignee" total.

5. Time Logging: If team members log their work against issues, this reduces the "Remaining Time Estimate." Ensure that the logged work is reflected accurately and that the "Workload by assignee" reflects these updates.

6. Shared Work: In some cases, work might be assigned to more than one individual or shared among team members, but not accurately reflected in Jira. This could affect how workload is calculated if Jira's configuration does not account for shared assignments.

[Ankush Bora]

I do not know enough about this column. However, based on assumptions, I would think this would be : Remaining time = Estimated time - Logged time

You may verify this by reviewing the difference of these mentioned columns.

Do let me know if you find a clue to that.