• 1,099
    • 129
    • 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.

      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
      • App data (third-party apps)
      • Etc.

      Workarounds: 

      1. Check if the following paid addon helps -  Deep Clone for Jira This is how the clone option of this addon looks like:

      2. A different option would be to use Automation for Jira for the process. The following rule shows an example of how to create such a rule: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/9918982/207129031 

            [JRACLOUD-5052] Allow different "Clone Issue" options

            Darío Teresa added a comment -

            Pls give us the oportunity to clone or copy the comments... 20ys issue

            Darío Teresa added a comment - Pls give us the oportunity to clone or copy the comments... 20ys issue

            I wish I could add a *.gif to this feature request... there would be millions of funny memes on this one.

            20 years an still no progress. Just close it and take the anger of the community with pride.

             

            Christian Schneider added a comment - I wish I could add a *.gif to this feature request... there would be millions of funny memes on this one. 20 years an still no progress. Just close it and take the anger of the community with pride.  

            Mark Caldwell added a comment - - edited

            Yup 20 years is a bit long on a ticket. Upvotes on this one are way low. It's a good request I see no reason not to do it. Not having this wastes hours of my precious time looking for workarounds. Please implement.

            Mark Caldwell added a comment - - edited Yup 20 years is a bit long on a ticket. Upvotes on this one are way low. It's a good request I see no reason not to do it. Not having this wastes hours of my precious time looking for workarounds. Please implement.

            Cam S added a comment -

            Dear JRACLOUD-5052,

            I know I’m a bit late, but I couldn’t skip wishing you a fantastic start to your 20s!

            You’ve been wished for, dreamed of, and maybe even whispered about for two decades… and today, we are still waiting for you! 

            Happy belated 20th birthday.

            Here’s to maybe making a start on this request this year!

            Cam S added a comment - Dear JRACLOUD-5052 , I know I’m a bit late, but I couldn’t skip wishing you a fantastic start to your 20s! You’ve been wished for, dreamed of, and maybe even whispered about for two decades… and today, we are still waiting for you!  Happy belated 20th birthday. Here’s to maybe making a start on this request this year!

            A key function for this request is the ability to deep clone from the issue hierarchy levels above Epic.

            Darrel Jackson added a comment - A key function for this request is the ability to deep clone from the issue hierarchy levels above Epic.

            Curious why it takes Atlassian 20 years to determine interest. I think the interest is pretty clear and that Atlassian needs to get off your butt and get this done. This should be considered a basic feature functionality.

            Gene Ferguson added a comment - Curious why it takes Atlassian 20 years to determine interest. I think the interest is pretty clear and that Atlassian needs to get off your butt and get this done. This should be considered a basic feature functionality.

            Hello !
            I would like to know when this solution will be released in Jira, as I am having a problem with slow queues because I have to create two automations to supply one, as the clonings I do are not bringing the comments and I have to generate another automation to copy the comments, this way if this tool is inserted into Jira I will no longer have this second demand and this will speed up my internal company processes.

            Rodrigo Magnani da Silva added a comment - Hello ! I would like to know when this solution will be released in Jira, as I am having a problem with slow queues because I have to create two automations to supply one, as the clonings I do are not bringing the comments and I have to generate another automation to copy the comments, this way if this tool is inserted into Jira I will no longer have this second demand and this will speed up my internal company processes.

            I would suggest that it be clear when cloning that deleting things in the clone will affect the original ticket. Also, functionality for copying (and not cloning) would be helpful to add. In this way, deleting parts of the copy (not clone) would not affect the original.

            Natan Hoffmann added a comment - I would suggest that it be clear when cloning that deleting things in the clone will affect the original ticket. Also, functionality for copying (and not cloning) would be helpful to add. In this way, deleting parts of the copy (not clone) would not affect the original.

            Are you serious!? A ticket from 2004?

            Alrik Adersin added a comment - Are you serious!? A ticket from 2004?

            Please enable comments to be cloned whilst performing automation. Please also allow for projects as a whole to be cloned. 

            Dunn, Nicola added a comment - Please enable comments to be cloned whilst performing automation. Please also allow for projects as a whole to be cloned. 

              9aed6e7b8ed1 Shikhar Pahadia
              59beb99a3f88 Robert Christensen
              Votes:
              496 Vote for this issue
              Watchers:
              283 Start watching this issue

                Created:
                Updated: