Linking a cloned issue to the original via automation

[Neil Womack]

Hello, I am trying to configure a rule that automatically clones a ticket to another project, assigns the clone to the same user as the original and then links the cloned ticket back to the original. I have it working except for the last step, as it never links back to the original. Here is my automation:

From researching the other posts in this forum I have verified that the rule is scoped for multiple projects and includes both the source and destination projects in the scope.

I have also confirmed that the Link issues outlined in the last step of the automation exist in the source project (below):

The issue is automatically cloned with the proper assignee, but still does not link back to the original issue. Is there something else I'm missing?

[Mohammed Shakhib]

This topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have any more questions, feel free to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our  Community Guidelines .

Cheers!

[Clara Belin-Brosseau_Elements]

Hello @Neil Womack

If you're seeking for an easy way to clone an issue to another project and link them together while keeping the same assignee, 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).

You can check our guide here.

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

[Bill Sheboy]

Hi @Neil Womack -- Welcome to the Atlassian Community!

After you clone the issue, add a branch to Most Recently Created Issue before the Link Issue action.  That will change the context to the new issue, rather than the trigger one.

• trigger: issue created
• action: re-fetch issue (I recommend always adding this action after the Issue Created trigger to prevent timing problems where some data may not be ready when the rule starts.)
• condition: assignee is ... (your check on the trigger issue assignees)
• action: clone issue
• branch: to most recently created issue
  • action: link issue

Kind regards,
Bill

[Neil Womack]

Thank you very much Bill, that solved the problem! For anyone else who may benefit, here is the final automation:

[Shivani Saran]

Hi @Bill Sheboy I implemented this automation in same way, but this is not working for in my case

issue is getting cloned, but it is not getting linked with original issue

[Bill Sheboy]

Hi @Shivani Saran -- Welcome to the Atlassian Community!

Please post images of your complete automation rule, the action where the linking occurs, and of the audit log details showing the rule execution.  Those will provide context for the community to offer suggestions.  Thanks!

Until we see those...

Are the issues all in the same Jira project or different projects?

Kind regards,
Bill

[Vasu]

Hi @Bill Sheboy ,

I have also implemented this automation in same way without assignee , but this is not working for me.

issue is getting cloned, but it is not getting linked with original issue.

Refer  below. the automation flow used. Request to provide if you have any suggestions to work

 

[Bill Sheboy]

Hi @Vasu -- Welcome to the Atlassian Community!

As this is an older thread, I recommend creating a new question, perhaps including a link back to this one, to ensure the maximum number of people see it to offer suggestions.

Until we see your new question...

Are your issues in multiple projects?

If so, the rule scope is likely single-project and so the issue linking cannot happen.  (Single-project scope rules may create issues in other projects but they cannot access them otherwise.) 

The two ways to solve that are:

• Add the issue link at the same time the issue is created / cloned
• Change the rule scope to multiple-project, including all relevant projects.  Your Jira Site Admin will need to help with that configuration change as it is a global automation configuration setting.

Kind regards,
Bill

[Vasu]

Thanks a lot ! @Bill Sheboy  for quick response. 

[Carey Aydelotte]

I had the same problem. Here's my solution:

1) Clone work item

2) Re-fetch work item data

3) Link work item to trigger work item

Mine is a global automation, which requires a Jira administrator to set up. It had to be a global automation because the original ticket (or trigger work item) is in a different space than the new ticket.