Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-12297

Moving an issue that belongs to a sprint across projects shouldn't move the sprint with it

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

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

      Problem Definition

      When an issue that's in a backlog gets moved from one project to another the sprint will come with it. That causes a lot of confusion if sprints are not being tracked across projects as the sprint will exist on both boards and changing one will change the other. In addition it's not possible to start the sprint unless you have administrator access across both boards and projects.

      Suggested Solution

      It's a tricky one to solve - but perhaps making the sprint field visible on the move issue process will make end users more likely to remove the sprint value.

      Workaround

      Manually remove the sprint value yourself.

      Attachments

        Issue Links

          is incorporated by

          Suggestion - JSWCLOUD-10935 Ability to move an issue without copying Agile sprint information

          • Closed
          is related to

          Suggestion - JSWSERVER-12297 Moving an issue that belongs to a sprint across projects shouldn't move the sprint with it

          • Closed

          Activity

            People

              Unassigned Unassigned
              mhunter Matthew Hunter
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: