At present on my JIRA instance the time tracking settings is set to 1 day = 24 hours.
Which means, for an issue (original estimate of 1 working day) if someone logs work for 8 hours (which is effectively one working day), the system still displays 16 hours in remaining hours.
I understand that the fix is to go to time tracking and amend the setting to 1 day = 8 hours. But, if I do that the system screws up the original estimates for all issues.
If I make this change an old issue (with an earlier original estimate of 3 days) after the change now starts showing an original estimate of 9 days (since the esimate is stored in seconds and was earlier divided by 24 to get days but now is getting divided by 8 and hence tripled).
How do i get round this problem?
I have checked the option of jelly scripts and I could not find a solution using jelly.
Any ideas guys?
The default in JIRA to my knowledge has always been 8 hours, so at somepoint someone changed it to 24.
You would have to use the issue navigator to target all issues with an estimate > 8 hours estimated during the window when it was changed, and re-estimate those tasks.
You could most like do this with a jelly script, or an external script using the REST interface.
I understand it may not be the magic bullet you were looking for, but I am not aware of any other way.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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