Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-76173

Bulk change no longer clear the sprint field value containing completed sprints.

    XMLWordPrintable

Details

    Description

      Summary

      Users were able to remove issues from completed sprints via bulk change.
      Right now, the bulk change action no longer remove completed sprints from issues.

      Atlassian Community post: How do I remove an issue from a completed sprint?

      Steps to reproduce

      1. Have an issue associated to a completed sprint.
      2. Open the JIRA issue search.
      3. Search for this issue.
      4. Perform a bulk change.
      5. Select Change Sprint Field and leave the sprint field value empty.
      6. The bulk change will remove future and active sprints from the issue, but not the completed issues.

      Expected Result

      The bulk change sprint field action will clear the sprint field value (including completed sprints).

      Actual Result

      The bulk change sprint field action will remove active and future sprints but keep completed sprints.

      Also when issues only have completed sprint(s) added as values in the Sprint field, an entry stating that the field was cleared will be created in the issue history even though the value(s) persists:

      Workaround

      • Create a new sprint in the backlog
      • Get its ID:
        • You can do so by hovering over the ellipses button next to the sprint and then checking the URL:
      • Bulk edit the affected issues using the ID obtained from the previous step
      • That operation will replace all values in the Sprint field of the issues, including completed sprints
      • After that you can bulk edit the issues again to clear the value, or delete the sprint you created for that purpose

      Attachments

        Issue Links

          Activity

            People

              viyer@atlassian.com viyer
              aschneider@atlassian.com Adalberto Schneider
              Votes:
              254 Vote for this issue
              Watchers:
              184 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: