Uploaded image for project: 'JIRA Server (including JIRA Core)'
  1. JIRA Server (including JIRA Core)
  2. JRASERVER-5052

Allow different "Clone Issue" options



    • 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 An updated workflow for server feature suggestions.
    • UIS:


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

      Atlassian Update – 13 Jan 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.

      This suggestion is important for the JIRA development team, but we have not scheduled work and cannot provide an estimate on this. However, there is related work in progress, specifically JRA-7824 and GHS-6541.

      I also encourage you to browse the Atlassian Marketplace for issue cloning add-ons. You might find add-ons that meet your requirements there.

      Daniel Franz
      dfranz at atlassian dot com
      Principal Product Manager, JIRA Platform

      The new clone functionality is very useful. It would be really great if we could control what parts of an issue was cloned. For instance:

      • Clone entire issue (subtasks, comments, worklog, everything)
      • Clone with subtasks only
      • Clone with new reporter
      • Clone without subtasks
      • Etc.

      Hopefully you get the idea.


          Issue Links



              • Assignee:
                chrisrh Robert Christensen
              • Votes:
                265 Vote for this issue
                160 Start watching this issue


                • Created: