Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Report remaining time estimate on tickets in a Sprint not in Done

Sean Markus November 17, 2022

Hello,

Our team is trying to run a report to see how much estimated time is left in our Sprint. To do that it would count up the estimated time on tickets in a specific Sprint, in any category except Done.
Clicking "Workload by assignee" almost gives us what we need, showing the total time remaining in the sprint, but it counts tickets that are marked as Done as well.
The Time Tracking Report looks interesting, but it can only filter by Fix Version, not Sprint. So we'd have to label each ticket in the Sprint with a specific fix version, which is not ideal. I'm also not sure if tickets in Done are filtered out.
How can we accomplish this?

1 answer

1 vote
__ Jimi Wikman
Community Champion
November 17, 2022

By the description, I assume you are using a team managed project and not a company managed?

In Company managed you have multiple reports like burndown/burnup reports and the sprint report that seem to fit what you are looking for?

Sean Markus November 17, 2022

Thanks you for that information. We are company managed. The sprint report is interesting but does not seem to report a total remaining time. The burndown report shows a total remaining like we would need, but it seems to have the same issue as "Workload by assignee" where tickets in Done cannot be filtered out. 

 

It looks like we have these options:

  • Zero out remaining time on tickets moved to Done
  • Calculate by hand the remaining time on tickets in the sprint not in Done
  • Transition our reports from being based on hours to being based on story points. We understand this is basically the industry standard but just haven't been able to take the plunge yet
Like __ Jimi Wikman likes this
__ Jimi Wikman
Community Champion
November 18, 2022

You should always remove any remaining time when closing an issue, as there is no remaining time if it is closed. I suggest you add time management to the close screen and add a global automation for setting remaining time to zero if someone misses doing so in the transition.

I strongly urge you NOT to use Story Points unless your team is completely isolated from all other teams and never have any dependencies. That is because story points are useless for planning, as they are arbitrary and have no common value across teams.

If you always set estimates on story level, then you can also see time in the sprint in the gray, blue and green icons above each active sprint, or below for inactive sprints.

Like Sean Markus likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events