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

Bulk edit and of Sprint field and Bulk Move will remove issues from closed sprints

XMLWordPrintable

      Issue Summary

      When a sprint is closed but it still have open issues, then the issues go back to backlog (or a new sprint). If an user tries editing the sprint field on one of these issues, he has the option to add a new value but he can't remove the closed sprint. When the sprint field is edited through 'Bulk Operation' (Edit or Move), the closed sprint is removed from the field and so a new value is added instead of keeping both.

      Steps to Reproduce

      1. Create a sprint
      2. Create an issue and add it to the sprint
      3. Close the sprint and move open issues to backlog
      4. Open the issue created on step 2 and try editing sprint field
      5. You won't be able to remove sprint created on step 1 however you'll be able to add a new sprint
      6. Run a search that returns that issue, then choose Tools > Bulk Change > Select the issue
      7. Choose Edit option then enter a new value for sprint field
      8. Open the issue created on step 2, there'll see the sprint created on step 1 is no longer shown on sprint field

      Expected Results

      Issue should keep closed sprint information.

      Actual Results

      The value of sprint field is replaced.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSWSERVER-21518] Bulk edit and of Sprint field and Bulk Move will remove issues from closed sprints

            genelewin added a comment -

            To the extent that "gathering impact" status means you want to hear from people who are incredibly annoyed by this bug, please add my name to the list.  I just happened to notice this after doing a bulk edit to move items to a new sprint ... this is a bad oversight.  Please fix.

            genelewin added a comment - To the extent that "gathering impact" status means you want to hear from people who are incredibly annoyed by this bug, please add my name to the list.  I just happened to notice this after doing a bulk edit to move items to a new sprint ... this is a bad oversight.  Please fix.

            Chuck V added a comment -

            Hey Atlassian team - Since you're migrating this issue report from JSWSERVER-13333 , I think you should copy over the Watchers and Votes field also!!! 
            IMHO It's not fair to set this issue back to 0 interest, just because you need the ticket in a different queue.

            Please help us keep the attention this request deserves?

            Chuck V added a comment - Hey Atlassian team - Since you're migrating this issue report from JSWSERVER-13333 , I think you should copy over the Watchers and Votes field also!!!  IMHO It's not fair to set this issue back to 0 interest, just because you need the ticket in a different queue. Please help us keep the attention this request deserves?

            Javier Andres Orellana Orellana added a comment -

            we have 8.20.10 version affected too

            Javier Andres Orellana Orellana added a comment - we have 8.20.10 version affected too

              Unassigned Unassigned
              255109c6c964 Maria Marzec
              Affected customers:
              24 This affects my team
              Watchers:
              26 Start watching this issue

                Created:
                Updated: