-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
Component/s: None
-
1
-
Severity 3 - Minor
Summary
If an issue is created in JIRA and the Original Estimate Value is manually set to 0 (Zero) when time is logged, the Work Ratio value shows a large value
Environment
- JIRA v7.2.0-OD-03-014
- JIRA Agile v7.2.2
Steps to Reproduce
presuming your Scrum Board is configured for Time Tracking and Original Estimate
- Create a new issue and manually set the Original Estimate value to 0 (ex: 0m, 0h, 0d, etc)
- Log work on the issue by using the More > Log Work
- On the Issue Navigator Screen, add the "Work Ratio" Column or export to CSV all Fields
Expected Results
Work Ratio does not show an incorrect value or shows Blank like an issue created with an Empty/Blank Original Estimate
Actual Results
Created 3 Issues:
- 9 has No Estimate (Original Estimate Field left Blank on creation)
- 10 has a 0m Original Estimate on Creation
- 11 has a 15m Original Estimate on Creation
Logged 15 minutes of work on all 3 issues, below screenshot is the results:
Notes
It appears that JIRA is trying to prevent 'dividing by 0' as the Work Ratio is calculated on Time Spent / Original Estimate
Workaround
Edit the Issue and Set the Original Estimate to the same value as Time Spent
OR
Edit the Issue clear the Original Estimate and Remaining Estimate fields
- is related to
-
JRASERVER-26751 Logging work on a issue with a zero estimate will result in a work ratio of 9223372036854775807%
-
- Gathering Impact
-