How to Update Status of Linked Issues Across Projects

[Simay Paksoy]

Hi All, 

We have two Jira projects: Let's say Project X and Project Y. Currently, we can successfully clone a bug from Project X to the Project Y project based on a specific status. The cloned ticket in Project Y is automatically linked to the original Project X ticket with the "clones" link type. When we open the Project Y ticket, we see that it is linked back to the Project X ticket with the "is cloned by" link type.

Now, I want to create an automation rule that works as follows:

1. When the status of the cloned ticket in the Project Y changes to In Progress, In Code Review, or Pending Fix, I want the original Project X ticket's status to be automatically updated to In Progress.
2. When the status of the cloned ticket in the Project Y changes to On Production, the original Project X ticket's status should automatically update to Done.

I created an automation rule with these steps:

• Trigger: Issue transitioned → Status changed to In Progress, In Code Review, or Pending Fix.
• Condition: Compare two values → {{issue.issueLinks.type}} equals is cloned by.
• Branch: For linked issues → Type: is cloned by.
  • Condition: Status equals In Progress.
  • Action: Transition the linked issue to In Progress.

However, the rule didn’t work as expected. I checked the audit log, and it shows this message:
“The following issues did not match the condition.”

Can you help me figure out what I might be doing wrong? Is there a better way to set up this automation to ensure the original Project X ticket's status is updated based on the Project Y ticket's status? In addition to that, we are using different workflows for each project. 

Any insights would be greatly appreciated!

[Florian Bonniec]

Hi @Simay Paksoy 

Is your automation scope on both project ?

Which condition is not met, the 1st or 2nd one ?

It may be related to the 1st one where you should not use 'is cloned by' but Cloners

Regards

[Simay Paksoy]

Hi @Florian Bonniec thanks for your answer. Automation should work in the first project. In other words, the status of the first ticket created should be updated according to the status of the ticket created as a clone. However, I couldn't achieve this, I'm not sure if it was because different workflows were used.

[Florian Bonniec]

Did you try to compare issue.issuelink.type with Cloners ?

[Simay Paksoy]

Yes, I did it. But still, it doesn't work 

[Florian Bonniec]

I would remove this condition. For me issue.issueLinks.type is not returning what you are expecting but it's not really useful as it will branch over 0 issues if any.

Regards