Summary

CSV import of remaining estimate still shows in the Burndown chart even if the value has been manually changed (through UI)

Environment

Atlassian Cloud

Steps to Reproduce

1. Have a CSV file to import issues in JIRA and an issue with a Remaining Time estimate of 12w 3d 3h
2. Import a CSV file with mapping the Remaining Estimate Field
3. Edit the issue to have Original Estimate of 3h and Remaining Estimate of 3h.
   • 
4. Issue History shows:
   • 
5. Add the issue to a Sprint
6. Start the Sprint
7. Complete the issue
8. Check the Burndown Chart for Original Estimate and Remaining Estimate

Expected Results

The remaining estimate for the issue is considered as 3h

Actual Results

The remaining estimate for the issue shows 12w 3d 3h

The Original Estimate shows 3h

Notes

Manually editing the Remaining Estimate for field that was not imported using CSV works as expected;

Workaround

-