How to close a linked issue when an issue is closed using automation?

[Jamshaid]

I have two differrent projects TM and CO. Each issue in TM has a clone in CO created using Jira automation. 

Here is the link between both on the UI

• TM - is cloned by- CO
• CO - clones - TM

I want to close the TM ticket when a CO ticket is closed. I am unable to find a way to do this.

I have tried Transition issue -> Done using automation but it looks like it does not work for the linked project. I have got the linked issue using 

{{#issue.issuelinks}}{{#if(equals(type.name,"Cloners"))}}{{outwardIssue.key}}{{^last}}, {{/}}{{/}}{{/}}

and the resulting key is stored in a variable. How do I close this parent issue? I can create automation in both TM and CO projet.

Thanks

[Jerrold - Empyra · Accepted solution]

Hi 

You can try using the following automation.

This automation operates by checking for linked issue types when a ticket is transitioned to the "done" column. If the linked issue type is "clones," it will then move the parent issue to the "done" column.

Thank you.

[Jamshaid]

@Jerrold - Empyra Thanks for responding. I have tried this and it does not work. 

Here is the result

Here is my rule

Here is the relevant issue

Could you please guide what's wrong on my side? I am an admin in both projects. 

[Jerrold - Empyra]

After transitioning the CO-20 to the Done status, could you please refresh the page once or twice and then check it?

[Jamshaid]

@Jerrold - Empyra It ended up with the same issue after relogin and several refreshes

[Jerrold - Empyra]

Could you kindly provide the audit log and review the workflow of TM-69 to confirm if there are any conditions or validators in place before transitioning to the "done" status? Additionally, please verify the scope of the automation rule. I have set my scope as global, but you can set it for the two projects.

[Jerrold - Empyra]

And Please ensure that the rule actor has the necessary permissions in the project. If the rule actor is Automation for Jira, kindly assign the Atlassian-addons-project-access role or update the rule actor to your name.

[Jerrold - Empyra]

The automation rule is functioning as expected for me, which is why I am asking to check all these things. Apologies for any inconvenience.

[Jamshaid]

@Jerrold - Empyra 

Thanks a lot. The Project permissions was the issue. I updated permissions of automation rule to both projects and it worked perfectly.