Roll-up estimate/remaining hours for a sprint by user

[Mike Marshall]

We are looking to get better visibility into the work assigned to each Scrum team member during a sprint by having members estimate sub-tasks. I thought the "Workload by assignee" would provide this roll-up based on who was assigned to the sub-task; however, it appears to roll-up based on who owns the issue. Since multiple people work on a single issue this does not accurately reflect the workload at the individual Scrum team member level.

Is there a way to view the sprint workload by the sub-task assignee?

[Mike Marshall · Accepted solution]

Thank you for the feedback. I've ended up creating an eazyBI report to generate this data. I'll also keep an eye on JSWSERVER-15109 to see if the issue gets resolved by Atlassian.

[Mehmet A _Bloompeak_]

Hi @Mike Marshall

An alternative way is to use Reports - Charts and Graphs for Jira app developed by our team.

• You can create custom, flexible and colorful bar charts and table views for any data you want/need.
• You can set X axis to be any parameter like Created(month), Assignee, Sprint, Fix Versions etc.
• You can set Y axis to be any parameter like number of issues, sum of remaining estimates, average of story points etc.
• You can group your data on any field(Sprint, Status, Assignee, Component, Project etc.) you want.
• You can choose various date ranges like All Time, Last Year, Last 3 Months, Last 6 Months etc.
• You can order the results by drag and drop.

Here is a sample report that shows sum of remaining estimate by assignee in current sprint.

Here is our live demo dashboard where you can see and modify sample reports and play with them.

Hope it helps.

[Dmitry Astapkovich _Colined_]

This is one of many use cases, where Pivot Report we develop can help



Here's a demo report you can play around with. 

Please note that you can choose one of three remaining time to be shown:

• default Remaining  
• Remaining Open (remaining time only from active issues)
• Remaining Unspent (remaining time from completed issues, an overestimate in other words) 

[Nic Brough -Adaptavist-]

Before we go into too much detail, can you confirm that you are not using time tracking for the sprint estimate here?  (time tracking = original estimate, remaining hours, worklogs etc)

[Mike Marshall]

I'm not sure I fully understand your question. I have the Sprint Board configured for Estimation Statistic = "Story Points" and Time Tracking = "Remaining Estimate and Time Spent". Is this what you are asking?

I've also performed some additional searching and found an open Bug, JSWSERVER-15109, that appears to identify the issue I'm trying to solve.

[Nic Brough -Adaptavist-]

Yes, thank you, it was exactly what I was asking for! 

I asked because some people use the time estimates as the sprint estimate (which is fine) and then put them on sub-tasks (which is nonsense in Scrum and hence breaks all your reporting)

Your settings are fine though.

And, yes, the bug you've found is the right one.  It's a little difficult to know what to do with it though - because the estimates do roll up to their parent issues, then you have a problem in that an issue assigned to X shows a time, but part of it is on an issue assigned to Y.  Y's estimation is fine, but it's not clear what to do with X's time.

[Mike Marshall]

Thank you for the confirmation. Do you know if there are any work around solutions to be able to provide a similar tabular view that would have Assignee on the Y-axis with the sum of "Remaining Hours" on the X-axis. I'm playing around with different dashboard options right now, haven't found any 2-dimentional options that include the "Remaining Hours".

[Nic Brough -Adaptavist-]

I generally head for reporting apps, but there's a lot of them in the marketplace!