Issue Summary

Using the new issue view, when attempting to enter a partial number decimal value such as ".5h" to represent a 30-minute increment or ".1h" to represent 6 minutes into the time tracking field while logging work on an issue will fail unless a "0" zero is added in front of the decimal, Noting the behavior is specific to Jira Cloud and works without issue in Jira Server causing a usability discrepancy and barrier of use when migrating Server to Cloud

Steps to Reproduce

1. Using New issue view
2. Log work on an issue
3. add a decimal value such as ".1h" or ".5h" or ".25h"

Expected Results

Time is logged on the issue per the decimal value input the same way it is done in Jira Server

Actual Results

It fails with the note:

You need to log time in the format 2w 4d 6h 45m

NOTE:

Works in classic issue view and Jira Server, the failure occurs in the New Issue view only

Workaround

add a "0" zero in front of the decimal, i.e. "0.1h" or "0.5h" or "0.25h"
Noting that In both Jira Server and Cloud beyond 2 decimal places the increment must be an increment of 5 as covered in:

• https://jira.atlassian.com/browse/JRASERVER-23559
• https://jira.atlassian.com/browse/JRACLOUD-23559