Issue Summary

When transitioning a ticket using time tracking as Days, Jira returns a 500 error.

It will occur whenever the "remaining time" estimate in the issue cannot be converted evenly from number of seconds to the current formatting and then back to whole minutes.

i.e. The remaining time estimate renders as 0.06d, which when converted back to seconds doesn't divide evenly into minutes

Steps to Reproduce

1. In time tracking menu (<sitname>/secure/admin/TimeTrackingAdmin.jspa) set the config for "Time display format" to "Days" and the "Default unit for time tracking" to minutes.
2. Pick an issue in the site and set the remaining time estimate on it to 29min or 0.06d
3. Ensure that the workflow for this ticket has a status transition with a screen which includes the time tracking field
4. Attempt to transition the relevant issue, setting a "time logged" to 1m

Expected Results

It's expected that when logging time to an issue, you should be able to transition the ticket without any issues, even if the user is using time remaining format in Days.

Actual Results

Jira returns a 500 error once you transition the issue.
As a result there are error logs in the Back-end saying: "Error occurred while converting time estimates:Durations must be in whole minutes"

Workaround

1. The workaround is to switch the site's formatting to "Pretty" in <sitname>/secure/admin/TimeTrackingAdmin.jspa
OR 
2. ensure the remaining time estimate when rendered as a fraction of a day always converts evenly to whole minutes (so 0.1d instead of 0.06)