Inquiry on Sprint Health Gadget

[Tristen John Bagain]

Hi,

Need to understand the algorithm used in the yellow section on the sprint health gadget. Is it based off the difference between Original Estimate and Time Remaining?

This page https://confluence.atlassian.com/agile064/jira-agile-user-s-guide/using-the-jira-agile-gadgets/using-the-sprint-health-gadget doesn't explain that part.

[Trudy Claspill · Accepted solution]

The first color block on the left is the total of your Estimation Statistic for all issues in statuses that are part of the "To Do" Status category. These statuses show as a gray lozenge.

The middle color block is the total of your Estimation Statistic for all issues in statuses that are part of the "In Progress" Status category. These statuses show as a blue lozenge.

The last color block on the right is the total of your Estimation Statistic for all issues in statuses that are part of the "Done" Status category. These statuses show as a green lozenge.

[Trudy Claspill]

What my questions stand is more on how that "4w 4d 5h" was calculated on the yellow. 

That is a good question.

My initial response was that it would be taking the sum of the Original Estimates on the associated issues and then pretty-printing it based on the Time Tracking global issue settings where working hours per day and working days per week is specified.

That is how the value appears to be calculated in my gadget.

I did note that if I changed the global settings for Time Tracking and refreshed the gadget the calculation did not change.

Also, I found that if I clicked on the bar to show the issues in the Navigator,

- sub-tasks in the "In Progress" statuses would be included in the navigator but did not appear to be included in the calculation displayed with the bar.

- the Original Estimate values displayed in the navigator did rely on the current global settings for Time Tracking.

My initial global settings had a 40 hour work week, and the bar calculation showed 1 week for the 40 hours I allocated to the Original Estimates of the In Progress tasks. Then I changed the global settings to an 80 hour work week. When I refreshed the gadget the bar calculation still showed 1 week. But when I clicked on the bar and showed the issues in the navigator, the Original Estimate pretty print calculations were all displayed in terms of an 80 hour work week. So where an 8 hour estimate would've shown 1 day for a 40 hour work week, in the navigator it showed 8 hours instead, and an estimate for 16 hours showed 1 day instead of 2 days in a 40 hour work week.

So I'm not entirely sure how the bar is determining the hours per day and days per week for pretty printing the calculations in the gadget.

[Tristen John Bagain]

Thanks @Trudy Claspill for the input. I guess wasn't accurate. What you illustrated is something I do understand. What my questions stand is more on how that "4w 4d 5h" was calculated on the yellow. I tried to calculate it manually by 1) clicking that bar 2) extract the result of the filter and 3) and do a sum of the "Original Estimate" field. The manual calculation below is no where close on what the health gadget shows. The difference is almost a week

[KH_Jean]

@Andrew James  this topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have additional questions, we encourage you to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our Community Guidelines.

Thanks!

[Andrew James]

The yellow section in the Jira Sprint Health Gadget shows the total Original Estimate of all issues that are currently marked as "In Progress". It does not use the Time Remaining field for its calculation.

Here are the key points:

• It adds up the Original Estimate values for all issues in "In Progress" status.

• The displayed time format (like weeks, days, hours) follows your Jira instance’s time tracking settings.

• If you change those settings (like hours per week), the gadget may not update visually right away, even though the raw data reflects the new settings.

• This can cause differences between what the gadget shows and what you see in the issue navigator.

So, the yellow bar is based solely on original estimates for ongoing work.