Jira Cloud Automation Cloning issues between projects with Comments

[Brian Taylor]

Jira Cloud Automation Cloning issues between projects with Comments. I have tried the article published by Atlassian, https://confluence.atlassian.com/jirakb/how-to-copy-comments-from-the-original-issue-to-the-cloned-issue-1236601599.html, but it returns "No Action Performed" once the issue is cloned to the new project.  

[Clara Belin-Brosseau_Elements]

Hi @Brian Taylor

Automation rules are often prone to errors and pretty hard to maintain on the long term. It becomes even more true when you have a large number of rules running.

As an alternative, I can suggest trying our app Elements Copy & Sync to clone issues with their comments. It should save you a lot of time. 

You can also synchronize the work items together if needed so that if someone comments the source issue, the comments also appear in the clone issue. Synchronization can be one or two-ways.

Don't hesitate to check the documentation, it’s really quick and easy to set up.

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

[Luka Hummel - codefortynine]

Hi @Brian Taylor,

If you are willing to use a marketplace app, our app Deep Clone for Jira removes these cloning road-blocks in one go. From a single dialog you can clone one issue or 100 000 and carry over:

• Comments – with original timestamps and authors intact
• Attachments, work-logs, watchers, votes and even the current status
• Components, versions, sprints – they’re auto-created in the target project if missing

Need it hands-free? You can fire the same clone via Jira Automation or a workflow transition: add the built-in post functions where your rule currently runs.

[arielei]

Hey @Brian Taylor 

Use 2 more actions:
1. Delay - after item has been created.

2. Re-fetch - after delay.

that should solve your issue.

Ariel.

[Brian Taylor]

Arielei

That did not seem to fix the issue - the comments are still not showing 

[Mikael Sandberg]

What is the link type on the cloned work item? Is it "clones" or "is cloned by"? The default is usually clones on the work item that is the clone of the original one. If that is the case here that would explain why your automation is not doing anything since it is looking for a link type of "is cloned by".

[Brian Taylor]

Mikael - I tried your suggestion, but it didn't work, and now I'm not getting any feedback in the logs.  I have attached both automation of the Clone and Comment copy for reference in case you see something else that maybe causing the issue

[Mikael Sandberg]

On the cloned work item, what is the link type used back to the original work item?

[Brian Taylor]

Both sides are set to Clones

[Mikael Sandberg]

Then I assume that you have changed the default link type, am I correct? As I mentioned above, the default is "is cloned by" as the outbound link on the original work item and "cloned" as the inward link on the cloned work item. 

On the automation that should copy the comments, under Rule details have you checked to enable other rules to trigger it?