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

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • None
    • None
    • 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.

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? 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.

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

                Created:
                Updated:
                Resolved: