The day remaining gadget always shows 1 day less. Also during some time in the day (I think around noon'ish or so) it will deduct one more day (as if I was in a different timezone). I checked my timezone and it is correctly reflecting my timezone.
The gadget calculates days left in 24 hour increments, so e.g. if there's 47 hours left until the end of the Sprint, it'll show 1 day left (although intuitively you may assume it's 2 days). The result of the calculation will change at the hour of the planned Sprint end time as well, as that's when an increment ends - in this case, it'll be around noon.
Totally agree with Paul and Roman. Bottom line, it always shows wrong data (less 1 day). It must be fixed.
More over, when starting a sprint, you define start and end time. It fails to calculate days in sprint as well. For example, I defined the start time as 08Aug2016 00:00 AM and end time as 18Aug16 23:59 PM. It should have calculated it as 9 days; actually it was 8..
I am seeing the same thing. For example, if there are 3 full days and some of the current day left in a sprint, it will show as 2 days remaining. It is rounding the days left down AND subtracting one, meaning that the last full day you have AND any additional time leading up to the sprint end are both 0 days remaining.
Doesn't make much sense, but that is apparently how they think it should work unless it can be configured.
Any news on this topic Atlassian? The Days Remaining on my dashboard just jumped from 6 to 4 as today, a Friday, came to a close. Only nonworking days are Sat/Sun My active sprint ends next week Friday 5:00PM so still have 5 full working days. Users should not come in to work on Monday morning, expecting to see 5 days remaining to work and be confronted with "4" displayed by this gadget. Help!
I agree with the comments above - pretty shocking that this is still not fixed in Jira.
Also happens in the confirmation screen before a sprint is launched. Set sprint start and end to be 9:00 Monday to 17:00 Friday and it says 4 days!
Pretty lame that this bug still exists (in the Cloud version, at least)...
@Carlton McFarlane, you mention "bug still exists". Are you aware of a bug being reported/tracked on this? I don't immediately see one and it has been my understanding that it is working as designed. Granted one could argue that the design could and maybe even should be changed.
Thank you for your response, @Jack Brickey.
Re: bug vs. feature - the issue I describe above could only philosophically be described as a "feature" rather than a "bug". See, in addition, the reports of @Mark Palnau and @Mark Luders above. It's improbable that someone proactively designed a full week to be shown as four days at or before the start of the week.
Re: existing issue report - I have no idea. I reached this thread via a fruitless Google search to try and find the settings where I fix this display issue or implement a workaround. It seems that working days are customisable but not working hours (except in Portfolio for Jira). Not acceptable that one should have to use a paid add-on to fix what appears to be a simple clock issue.
Happy to log an issue somewhere, although I'd have thought someone in the Atlassian team might have done that given this thread has been open for five years.
Where should I look/log?
Personally, I would find it to be a better (?) solution to report hours remaining and drop partial hours rather than days remaining. It would use a standard 8h day unless configured otherwise.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs