-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 5.0 - EAP, 5.0, 5.1.3, 6.1.5, 7.8.1
-
Component/s: Issue - Time Tracking & Worklog
-
5
-
5
-
Severity 3 - Minor
-
1
- Create a issue with a zero estimate.
- Log work on the issue.
- (BUG) Goto the issue navigator and look at the issue. Make sure the work ratio column is configured. Note the very large percentage.
Cause:
workratio = Logged Time * 100 / Original Estimate
When "Original Estimate" is 0 (and not undefined) the division returns max_int_64 = 9223372036854775807
Workaround:
For issues that already have an estimate set, change original estimate to 1m
Don't set original estimates to 0. The default value is "not defined" but can't be set back to that
- is related to
-
JRASERVER-14439 Logging work on an unestimated ticket results in work ratio of 2147483647%
-
- Closed
-
-
JRASERVER-36383 REST (get) issue throws error if WorkRate is very large
-
- Closed
-
- relates to
-
JRACLOUD-65484 Work Ratio Shows Large Number if Original Estimate was Set to 0
-
- Closed
-