Hi Atlassian,
I want to draw you attention on bug that we are facing at the time of Spint Closing and Staring a new Sprint from the Sprint Api end.
Flow we are following -- Closing the ongoing Sprint and then Starting a new sprint, but if you look into the api of Sprint detail's its
showing reverse, Sprint "startDate" time is before the last sprint "complete Date" time by 20-30 sec, which indicates that new sprint got started before the last sprint got closed which is not actually happening.
As we are using this Api in our project it leads some discrepancy.
Example:
https://nipponhcl.atlassian.net/rest/agile/1.0/board/81/sprint
{
"maxResults": 50,
"startAt": 0,
"total": 2,
"isLast": true,
"values": [
{
"id": 424,
"self": "https://nipponhcl.atlassian.net/rest/agile/1.0/sprint/424",
"state": "closed",
"name": "DotNet Sprint 1",
"startDate": "2024-02-07T10:47:00.000Z",
"endDate": "2024-02-20T11:17:00.000Z",
"completeDate": "2024-02-21T04:56:49.251Z",
"createdDate": "2024-02-06T10:07:40.567Z",
"originBoardId": 81,
"goal": ""
},
{
"id": 434,
"self": "https://nipponhcl.atlassian.net/rest/agile/1.0/sprint/434",
"state": "active",
"name": "DotNet Sprint 2",
"startDate": "2024-02-21T04:56:04.087Z",
"endDate": "2024-03-05T11:17:00.000Z",
"createdDate": "2024-02-21T04:55:57.280Z",
"originBoardId": 81,
"goal": ""
}
]
}
Here you can see that sprint id 434 "startDate": "2024-02-21T04:56:04.087Z" is before the "completeDate": "2024-02-21T04:56:49.251Z", of last closed sprint 424 but flow wise we are completing the sprint "id": 424 ("name": "DotNet Sprint 1") and staring sprint "id": 434("name": "DotNet Sprint 2") after that.
Please suggest.
Hi @Ankit -- Welcome to the Atlassian Community!
How are you completing one sprint and starting the next: manually, with your own code calling the REST API functions, with a marketplace addon, etc.?
If with your own code (or an addon), perhaps there is a timing problem where the new sprint is started before the previous one is completed.
Kind regards,
Bill
Hi Bill ,
No , I am not starting and closing the sprint with code calling the REST API functions, with a marketplace addon, etc.
I am doing it manually from UI , from the backlog of the Board.
Thanks
Ankit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information.
Are you creating the new sprint from the backlog, or are you creating the sprint from the Complete Sprint dialog and selecting the option "new sprint"? When I tried the second path I was able to cause a near overlap of sprints.
There is a related defect in the public backlog where burn charts are having overlapping sprint issues in the scenario like yours: https://jira.atlassian.com/browse/JSWCLOUD-26261
I recommend working with your Jira site admin to submit a support ticket for this symptom, showing them the steps you followed. https://support.atlassian.com/contact/#/
When you hear back from the support team, please post what you learn to benefit the community. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill ,
I am first completing the sprint by dialog complete sprint and then Starting a new sprint , you can have a look in Json response for sprint api .
Thanks
Ankit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.