-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
Component/s: Backlog - Sprints
-
4
-
Minor
Issue Summary
This endpoint update sprint doesn't work properly when updating some fieldsets as the completeDate updates to the current date time even though a different date time was passed in the payload.
Steps to Reproduce
- Create a sprint using this endpoint. This should create it in a future state
- Then use the update endpoint to update the sprint to an active state
- Once that is done, try to update the state to a closed sstate using the below data
{
"state": "closed",
"name": "sprint 1",
"startDate": "2020-04-11T15:22:00.000+10:00",
"endDate": "2020-04-20T01:22:00.000+10:00",
"completeDate": "2020-04-20T11:04:00.000+10:00",
"originBoardId": 5,
"goal": "sprint 1 goal"
}
Expected Results
{
"id": 37,
"self": "https://your-domain.atlassian.net/rest/agile/1.0/sprint/23",
"state": "active",
"name": "sprint 1",
"startDate": "2020-04-11T15:22:00.000+10:00",
"endDate": "2020-04-20T01:22:00.000+10:00",
"completeDate": "2020-04-20T11:04:00.000+10:00",
"originBoardId": 5,
"goal": "sprint 1 goal"
}
Actual Results
{
"id": 37,
"self": "https://your-domain.atlassian.net/rest/agile/1.0/sprint/23",
"state": "active",
"name": "sprint 1",
"startDate": "2020-04-11T15:22:00.000+10:00",
"endDate": "2020-04-20T01:22:00.000+10:00",
"completeDate": "2021-10-01T11:04:00.000+10:00",
"originBoardId": 5,
"goal": "sprint 1 goal"
}
The completeDate key seems to be ignored and follows the current date when the issue is updated.
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available.