Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-2581

Ability to copy issues from one project to another but with the ability to perform maintenance on one which updates both copies

    XMLWordPrintable

Details

    • 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

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

      Because we use the projects to manage our unapproved change requests/requirements, I need the ability to migrate approved requests/requirements over to our development project at the point where we have received said approval. I'd like to keep a copy of the original issue in both places so that our project mgrs can track the issue in their project and our developers can track the issue separately in their project (they may want to change the issue type, priority, etc).

      Would like to have the ability to make updates to the issue appear on both copies or on just one copy.

      Would like to keep this separate from moving, which causes the issue to lose its original numbering and which takes it completely out of a project, or linking, which simply links related/duplicated issues.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              bd3b6cbd37a8 Susan Moore
              Votes:
              13 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: