-
Bug
-
Resolution: Fixed
-
Low
-
5
-
Severity 2 - Major
-
Summary
Updating an issue remainingEstimate value using REST API calls also updates the originalEstimate to the same value. Setting originalEstimate updates remainingEstimate also
Steps to Reproduce
- Add Time Tracking field to the Edit Issue screen for the project the issue you want to update belongs to
- Run the following REST API call to update the remainingEstimate value:
curl -D- -u EMAIL:PASSWORD -X PUT --data "{\"fields\":{\"timetracking\":{\"remainingEstimate\":\"3d 1h\"}}}" -H "Content-Type: application/json" http://INSTANCE/rest/api/latest/issue/issuekey
Expected Results
Only the remainingEstimate value is updated
Actual Results
Both, originalEstimate and remainingEstimate are updated to the same value:
"timetracking":{ "originalEstimate":"3d 1h", "remainingEstimate":"3d 1h", .... },
Workaround
Set both, originalEstimate and remainingEstimate. This way it works fine:
- REQUEST BODY:
{ "fields": { "timetracking": { "remainingEstimate": "55m", "originalEstimate":"2h" } } }
- RESULT:
[......] "timetracking":{ "originalEstimate":"2h", "remainingEstimate":"55m", "originalEstimateSeconds":7200, "remainingEstimateSeconds":3300 }, [......]
- relates to
-
JRACLOUD-64730 CSV import of Remaining Estimate overwrites Original Estimate in issue history
- Closed
- is resolved by
-
ISSUE-2578 Loading...
- mentioned in
-
Page Loading...