Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9983

Closing an issue in a planned (unstarted) sprint does not remove it from the sprint, causing errors when deleting the sprint

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Reproduction:

      1. Create a new sprint
      2. Create an issue and drag it into the new sprint
      3. Close the issue. The issue will now not be visible in the sprint on the planning board anymore.
      4. Delete the sprint using the "x" button.
      Result: Error: This issue cannot be edited because of its workflow status.
      Expected: When closing the issue, it is removed from the planned (unstarted) sprint, so the sprint can be deleted without errors.

            [JSWSERVER-9983] Closing an issue in a planned (unstarted) sprint does not remove it from the sprint, causing errors when deleting the sprint

            If I may add something to this. If your organization implemented "jira.issue.editable" = false to prevent closed issues from being edited. You will need to remove that if you want to delete sprints.

            Steven Camilleri added a comment - If I may add something to this. If your organization implemented "jira.issue.editable" = false to prevent closed issues from being edited. You will need to remove that if you want to delete sprints.

            Tarun Sapra added a comment - - edited

            @Karie- Yes your correct about the "Completed sprint field" not being editable or making it editable, it can't be edited manually, but when the issue is in closed state then when JIRA internally tries to update this field then it can't because the closed state of the issue doesn't let JIRA do that resulting in the error which you described - Please see here - https://answers.atlassian.com/questions/254732/attempt-to-delete-empty-sprint-returns-error-this-issue-cannot-be-edited-because-of-its-workflow-status

            Tarun Sapra added a comment - - edited @Karie- Yes your correct about the "Completed sprint field" not being editable or making it editable, it can't be edited manually, but when the issue is in closed state then when JIRA internally tries to update this field then it can't because the closed state of the issue doesn't let JIRA do that resulting in the error which you described - Please see here - https://answers.atlassian.com/questions/254732/attempt-to-delete-empty-sprint-returns-error-this-issue-cannot-be-edited-because-of-its-workflow-status

            @Tarun - That doesn't work. Completed Sprint field is not an editable field and there is no option to make this an editable field. It is a field that Agile automatically adds to the view; it's not a field that can be added to any screen and be able to edit.

            Karie Kelly added a comment - @Tarun - That doesn't work. Completed Sprint field is not an editable field and there is no option to make this an editable field. It is a field that Agile automatically adds to the view; it's not a field that can be added to any screen and be able to edit.

            @Karie, if you update the property of the closed state of the workflow such that the issues are now editable, then you should be able to delete the sprint, because deleting the sprint means removing it's value from the issues which contain it, but if the issues are closed then the workflow properties make the issue non-editable, thus make the issues editable even when in closed state and then delete the sprint.

            Tarun Sapra added a comment - @Karie, if you update the property of the closed state of the workflow such that the issues are now editable, then you should be able to delete the sprint, because deleting the sprint means removing it's value from the issues which contain it, but if the issues are closed then the workflow properties make the issue non-editable, thus make the issues editable even when in closed state and then delete the sprint.

            I am unable to to delete a sprint - get this same error "This issue cannot be edited because of its workflow status" even when no issues exist in the sprint. We ran into the same issue as @Simon. We did have some issues when we were doing some future sprint planning. But, have since moved all of those issues out of the sprint into others or backlog to where no issues exist in the sprint or have closed issues that were related to the sprint that were duplicates. But, because they are closed, the sprint cannot be deleted and you have no way of seeing these because the sprint was never started.

            Karie Kelly added a comment - I am unable to to delete a sprint - get this same error "This issue cannot be edited because of its workflow status" even when no issues exist in the sprint. We ran into the same issue as @Simon. We did have some issues when we were doing some future sprint planning. But, have since moved all of those issues out of the sprint into others or backlog to where no issues exist in the sprint or have closed issues that were related to the sprint that were duplicates. But, because they are closed, the sprint cannot be deleted and you have no way of seeing these because the sprint was never started.

            David Yu added a comment -

            As a workaround, you can bulk-edit the single ticket "issuekey=XYZ-123" and clear out the sprintId field.

            David Yu added a comment - As a workaround, you can bulk-edit the single ticket "issuekey=XYZ-123" and clear out the sprintId field.

            Agree with Simon that the same cause can have multiple effects. If those items in future sprints had any story points, but are cancelled before the sprint starts, that story point value shows up in the velocity of that sprint.

            Dan McGarry added a comment - Agree with Simon that the same cause can have multiple effects. If those items in future sprints had any story points, but are cancelled before the sprint starts, that story point value shows up in the velocity of that sprint.

            This behaviour also means that if an issue in a future sprint is closed before that sprint start it will disappear from the plan mode, but will then show in the sprint as closed once then sprint is started.

            Simon Jarvis added a comment - This behaviour also means that if an issue in a future sprint is closed before that sprint start it will disappear from the plan mode, but will then show in the sprint as closed once then sprint is started.

              Unassigned Unassigned
              63ec319ffe6b Peter Schutte
              Affected customers:
              15 This affects my team
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: