Access Jira linked issues in a JSM automation

[Nancy Tinder]

I have JSM Incident issues that are cloned and the clone moved to another JS project. I am trying to create an automation that is scheduled for 2-3 times a day to run through all open JSM Incident issues, look at the linked issue in JS and close the JSM issue if the JS issue is Done. 

I grab the JSM list from the scheduled step with JQL, then step through the list with a For Loop step. I was hoping that it would grab the linked JS issue where I could test it and transition the JSM issue to Resolved if the JS link is Done. In the log, it never finds issues other than in the JSM project and the "make sure this works" button in the Linked Issues step brings back tons of records where I had hoped it would bring back just one.

Is this possible to do from within JSM? I am trying not to have to build automations on the JS side as there are several projects and they create new ones all the time so would be a nightmare to keep up with.

I have made it work looking at sub-tasks from within the same JSM project (close the issue if all sub-tasks are closed), but that template doesn't work across JSM and JS projects.

[Bill Sheboy]

Hi @Nancy Tinder -- Welcome to the Atlassian Community!

Short answer: the likely cause is the rule is using single-project scope (in the details at the top) and so cannot see the other issues.  Please work with your Jira Site Admin to update the rule's scope with the global admin permissions.

If that does not help, context is important for the community to help.  Please post the following:

• an image of your complete automation rule in a single image for continuity,
• an image of the rule details at the top of the rule,
• images of any relevant actions / conditions / branches,
• an image of the audit log details showing the rule execution (with all the areas expanded), and
• explain what is not working as expected and why you believe that to be the case.

Kind regards,
Bill