-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Component/s: Board - Sprints
-
4
-
Minor
-
3
-
Warranty
Issue Summary
Sprint can't be deleted from the Jira board if associated with Archved Jira tickets
Steps to Reproduce
- Add Manage sprint and schedule issue permission.
- Create Sprint
- Add a Jira ticket to the sprint
- Archive Jira ticket
- Delete sprint
Challenges: - JQL search for the sprint, Reports, Sprint/Board etc will not return Archived Jira tickets. Hence, it looks empty. - There are no explicit details that show Sprint deletion is blocked due to Archived Jira issues.
Expected Results
Sprint should be deleted if the user has necessary permissions (Manage sprint & schedule issue)
Actual Results
Sprint can't be deleted, and receive below details in browser logs
{
"errors": [
{
"message": "We couldn't make that happen because you don't have Schedule Issues permission.",
"locations": [
{
"line": 2,
"column": 9
}
],
"path": [
"deleteSprint"
],
"extensions": {
"status": [
401
],
"statusCode": 401,
"errorType": null,
"operationName": "BacklogDeleteSprint",
"tenantId": "abcd1234567890qwe",
"userMessage": "We couldn't make that happen because you don't have Schedule Issues permission.",
"classification": "DataFetchingException"
}
}
],
"data": {
"deleteSprint": null
}
}
Suggestion:
- A clear message to provide cause(Issue archive in this case)
- A column under the archive list to display Sprints
Workaround
Unarchive Jira tickets, and proceed with Sprint deletion.
- is related to
-
JRACLOUD-93786 Sprint can't be deleted if issue associated with it is from an archived project
-
- Closed
-
-
JRACLOUD-93506 'Something's gone wrong' error while deleting sprints
- Gathering Interest