Details
-
Suggestion
-
Resolution: Duplicate
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When specifying an issue Original Estimate, we should be able to use decimal point for the estimate value, such as:
- 1.3d or 3.3
However, under certain time tracking configuration, inputting 2.3d value into Original Estimate will produce the following error:
- The original estimate specified is not valid
The steps to reproduce:
- Configure the Time Tracking, set the number of working hours per day to 7.5
- Try to create issue and specify 2.3d, and the problem is reproducible
Tested on JIRA 5.0, 5.1.x
Attachments
Issue Links
- duplicates
-
JRASERVER-23559 Time Tracking Field Does Not Accept Decimal Value That Is Not Multiple Of 5
- Closed
- relates to
-
JRACLOUD-30064 Original Estimate do not accept 2.3d value
- Closed
-
JRASERVER-23559 Time Tracking Field Does Not Accept Decimal Value That Is Not Multiple Of 5
- Closed
- mentioned in
-
Wiki Page Loading...