Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-10935

Ability to move an issue without copying Agile sprint information

    XMLWordPrintable

    Details

    • UIS:
      1
    • Support reference count:
      3
    • Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      Original summary: Sprint duplication choice or notification when moving an issue between projects

      Current behaviour

      When a ticket from Project A is linked to a sprint and is then moved from JIRA Project A to JIRA project B, the sprint is duplicated in project's B Agile board. Many users would like the sprint field to be cleared out or at least to be notified by the system that this issue is going to occur if he proceeds with this operation.

      Expected behaviour

      Option 1: Allow the users to configure in JIRA Agile if they want the sprint field to be cleared when the issue is moved to another project that is not filtered by the board, or if they want to keep the existing behaviour to duplicate the sprint in the new board as well.

      Option 2: Keep the existing behaviour but always notify the user that the sprint is going to be duplicated, so the users are not taken by surprise when sprints appear in different boards.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              pschaff Pietro Schaff (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated: