Issue Summary

When trying to transition an issue with log work required, Jira emits a message saying `Specify a valid value for Remaining estimate`. Even if we use a value like `0.38d`, which appears to be a valid value for that field using days as a time format in the Time Tracking metrics.

Steps to Reproduce

1) Go to the Issues -> Time Tracking Admin page and set Time display format to Days - this is supported
2) Input a Remaining Estimate value of 3h on an issue and click Save - this is supported, and this value is certainly a number of whole minutes
3) Include the Remaining Estimate field on a screen which is used in a transition - this is supported
4) Click on that transition for that issue - this is supported
5) Do Not edit the Original Estimate - Just click on Ready for Verification to complete the transition
6) The value which Jira has chosen to display in the Remaining Estimate field, which is the representation of 3h in units of days, which is a number of whole minutes, triggers an error message on an input value which the user has not entered. The value was placed in the field by Jira.

Expected Results

Jira would accept the value of 0.38d on the Remaining Estimate value, as it suggests in the time tracking bar, follow the screens with the success and error to the same value:

Actual Results

Jira is not accepting the 0.38d in the Remaining Estimate field, and it's showing up an error message saying "Specify a valid value for remaining estimate" when we move an issue from a status to another.

Workaround

One possible workaround is to change the Time tracking metric from days to pretty, as shown below. Which accepts any value you insert on the field and it's not going to request a integer multiple of 5.

To change that option, you need to follow the steps below:

• Go to https://YOURINSTANCE.atlassian.net/secure/admin/TimeTrackingAdmin.jspa
• Click on the Edit Global Settings button
• 
• Then change the "Time Display Format" from Days to Pretty
•