Cloned Issues not linking through cross-project automation

[Melissa Mattee Murphy]

I have an automation that clones an issue from Project A into Project B once it's resolved in Project A. The automation is working for the most part: the issue is created successfully in Project B, and all of the desired fields are copied over. However, the issues are not linking together like clones usually do. 

1. Issue linking is enabled
2. I (the rule owner) have link issues permissions.
3. Just in case, I changed the rule actor from "automation for Jira" to myself. That didn't fix it. 
4. I can manually link the two issues no problem after the clone is created.
5. I added an additional step in the automation to link the two issues as clones. Still doesn't work.
6. The audit log says the issues were linked as part of the automation (they weren't). 
7. I have an identical automation with two other projects, which is linking issues as expected.

Anyone run into this before? Any other troubleshooting tips before I open a ticket with Atlassian?

[Bill Sheboy]

Hi @Melissa Mattee Murphy 

What is the scope of your rule (in the details at the top): single-project, multiple-project, or global?

• All rules can create (or clone) work items into other projects.
• However, a single-project scope rule cannot access work items in other projects for view or update...but linking modifies both work items involved.

There are two ways to solve this limitation:

1. When the work item is cloned, add the link at the same time by selecting Linked Issues from the field dropdown
2. Change the rule scope so the additional Link Work Items action succeeds.  Your Jira Site Admin will need to help change the rule scope in the global automation settings.

Kind regards,
Bill

[Trudy Claspill]

@Bill Sheboy 

In my experience (and per the testing I just re-executed using Company Managed Software projects)...

- The Clones link is not automatically created between issues when the Clone action is used.

- One must explicitly set the Linked Issues "field" in the Clone action to create the clones/is cloned by link

- This can be done even when the project scope of the rule is just one project and the clone issue is created in a different project.

- When the rule is scoped for multiple projects and the destination of the Clone action is within scope, still the clones link is not automatically created.

[Bill Sheboy]

Thanks, @Trudy Claspill as I misread the question to add additional links: not the "clone" link.

Although the solution is the same: add the link when the work item is created or change the rule scope and use the separate action.

[Melissa Mattee Murphy]

 @Bill Sheboy  That was a good call out! But it didn't help. :(  I changed the scope to include both projects and the rule is saying it links the two but there is no related work item on either ticket.

[Melissa Mattee Murphy]

@Trudy Claspill Is this what you're suggesting? Because this is the final step of my rule.

[Trudy Claspill]

No. You add the link creation directly in the Clone action.

[Melissa Mattee Murphy]

@Bill Sheboy 

@Trudy Claspill 

I fixed it! I had to switch from "Trigger work item" in the screenshot listed above to "most recently created work item." 

[Trudy Claspill]

That makes sense. When it is a separate action it would be acting against the Trigger issue, unless you had nested it within a branch For Most Recently Created Issue

[Clara Belin-Brosseau_Elements]

Hi @Melissa Mattee Murphy

As an alternative to Automation, which can sometimes be complex to configure and maintain, you might want to try our app Elements Copy & Sync. It allows you to easily clone issues from one project to another and automatically create links between the original and the copied issues.

It's very quick and easy to set up. 

The app is for free during 30 days (and it stays free under 10 users), so don't hesitate to give it a try.