Issue Summary

Agile sprint complete date value is not updated as expected using the REST API. 

The result is the same when sending the request with POST /rest/agile/1.0/sprint/{sprintId}. 

Steps to Reproduce

1. Create sprint using POST /rest/agile/1.0/sprint
   REQUEST: {"name":"Closed Sprint 1","originBoardId":"151","startDate":"2022-01-17T12:12:00+02:00","endDate":"2022-01-24T12:12:00+02:00","goal":"Closed Sprint 1 goal"}

1. Update created sprint PUT /rest/agile/1.0/sprint/{sprintId}
   REQUEST: {"originBoardId":"151","name":"Closed Sprint 1","state":"active","startDate":"2022-01-17T12:12:00+02:00","endDate":"2022-01-24T12:12:00+02:00","completeDate":"2022-01-26T07:18:29.572+02:00","goal":"Closed Sprint 1 goal"}

1. Update created sprint PUT /rest/agile/1.0/sprint/{sprintId}
   REQUEST: {"originBoardId":"151","name":"Closed Sprint 1","state":"closed","startDate":"2022-01-17T12:12:00+02:00","endDate":"2022-01-24T12:12:00+02:00","completeDate":"2022-01-26T07:18:29.572+02:00","goal":"Closed Sprint 1 goal"}

Expected Results

"completeDate":"2022-01-26T07:18:29.572+02:00"

Actual Results

The below exception is thrown in the xxxxxxx.log file:

Result:
id	:	236
state	:	closed
name	:	Closed Sprint 1
startDate	:	2022-01-17T10:12:00.000Z
endDate	:	2022-01-24T10:12:00.000Z
completeDate	:	2022-01-28T08:49:53.179Z
originBoardId	:	151
goal	:	Closed Sprint 1 goal 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available