Clone issue in another project and link cloned issue with original issue

[Shivani Saran]

Clone issue in another project and link cloned issue with original issue

[Walter Buggenhout · Accepted solution]

Hi @Shivani Saran and welcome to the Community!

Is this something you need occasionally / just once? Or do you want to do this regularly as part of a fixed process?

In the first scenario, you could just use Jira's built in clone issue feature. It creates a duplicate of the issue and automatically links it to the original issue. The downside of this is that the clone remains in the same project. So you would then have to move the issue to the desired target project. If this is a one-off operation, that should be perfectly feasible.

If you want to do this repeatedly, it might be better doing this via an automation rule. Here's a sample rule from the template library showing how you can approach this:

Hope this helps!

[Shivani Saran]

Hi @Walter Buggenhout Thanks for your response.

I created an automation for this, automation is working fine except "issue linking with original issue"

[Walter Buggenhout]

As you can see in the sample rule, you should be able to add the link issue action immediately into the clone issue action (see the detail in the last step of the screenshot I added earlier, where the Linked Issues field is filled out), so you don't need the branch and execute all in one go. 

If that still doesn't work, it might help if you could share any messages from the audit log.

[Shivani Saran]

@Walter Buggenhout I made the change you suggested in my workflow but I'm not sure where I am going wrong 

I am including audit log details and Workflow here for your reference

[Walter Buggenhout]

The link issue step should not be a separate step. Inside the Clone issue into ... action, add Linked Issues as a separate field and configure the link there. Remove that last action link issue to. It will not be necessary anymore.

[Shivani Saran]

@Walter Buggenhout Yeah, it's working fine. Thanks!!

@Walter Buggenhout  Is it possible to clone form attachment details as well from original to cloned issue.

[Walter Buggenhout]

That should work in exactly the same way, @Shivani Saran. Attachments is also a field you can include:

If the answer was helpful, consider marking it as accepted. That makes it easier to find for people looking for similar solutions. 👍

[Shivani Saran]

This (below mentioned) attached form detail I want to clone in cloned issue, the solution mentioned I implemented but I am not able to see these details in cloned issue.

Is it possible to clone this attached form details?

[Luka Hummel - codefortynine]

Hi @Shivani Saran and welcome to the community!

If you're looking for a more efficient way to regularly clone issues across projects and link them automatically, our app Deep Clone for Jira could be an ideal solution. It allows you to easily clone issues across multiple projects, preserving all details including attachments, comments, and links, while automatically linking the cloned issue to the original. This could simplify your process compared to manual automation rules.

You can also integrate Deep Clone in your existing Jira Automation. You can read more on that here.

[Clara Belin-Brosseau_Elements]

Hello @Shivani Saran 

There is another way to clone and link issues together that might be easier for you.

You can try our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc). Both apps are automatically linked together.

 

You can check the guide here. 

The app is for free during 30 days (and it stays free under 10 users).