Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-1558

Deep copy an issue to the same project or a single project



    • 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.
    • UIS:


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

      Atlassian Update – 4 January 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future. There are a large number of add-ons available in the Atlassian Marketplace that provide this feature.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Dave Meyer
      Product Manager, JIRA Platform

      Original request description

      As JIRA users we want the ability to copy / clone JIRA issues between multiple projects in such a way that all information related to the issue being copied is retained, specifically: summary, description, comments, labels, assignee and reporter, versions and components plus all the content stored in the custom fields.


          Issue Links



              • Assignee:
                mika.ruottinen@iki.fi Mika Ruottinen
              • Votes:
                314 Vote for this issue
                181 Start watching this issue


                • Created: