-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
2
-
Severity 2 - Major
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Importing a Remaining Estimate using a CSV shows as a change in the issue history. The change in issue history shows that both the Remaining Estimate and the Original Estimate have changed
- New Value for both = Remaining Estimate imported from CSV
The field values shows correct. The Original Estimate continues to show the value prior to the import. The Remaining Estimate shows the value imported.
Steps to Reproduce:
- Create issue with Original Estimate and different Remaining Estimate
- Export to CSV
- Change Remaining Estimate in CSV
- Import from CSV choosing Summary, Issue Key, Remaining Estimate.
- Review the history and estimate field values on the issue
Expected Behavior
Change History shows that Remaining Estimate changed without showing any change to Original Estimate
- is related to
-
JRACLOUD-67539 Updating the remaining estimate using REST API calls also updates the original estimate
- Closed
-
JRACLOUD-68302 CSV import of Remaining Estimate field value still shows in the Burndown chart even if the value has been manually changed (through UI)
- Closed
-
JRASERVER-64730 CSV import of Remaining Estimate overwrites Original Estimate in issue history
- Closed