Single Project Automation doesn't make edits to Issues in another project

[Alex Hall]

I'm working on some cross project automations.

When new issue is created in Project A:

• Check for text, if it matches, create new issue in Project B
• Close Project A
• Write a comment on the ticket in Project A and in Project B

However, the comment on Project B doesn't get written unless the rule includes Project B in the scope. But if I include Project B in the scope, then the rule runs for both Project A & Project B every time a new issue is created.

A similar problem for manually triggered rules

• When triggered in Project A, it creates issues in Project B (and C and D).
• If the Scope is expanded to include Project B, C, & D, then end users can see the rules which are designed to be triggered in their projects.
• But if the Scope isn't expanded, then actions in branches of "For: All created issues" or "For: Most Recently Created Issue" don't get executed.
• Actions when the Issues are created always execute, but you can't add a comment when creating a new issue.

Has the community dealt with this? Any suggestions to work arounds?

[Bill Sheboy · Accepted solution]

Hi @Alex Hall 

To make such multiple-project (or global) scope rules work as expected, please try using conditions to limit the processing.

For example, in your scenario:

• when issue created in Project A,
• look for matching issue in Project B, and when found
  • close the issue in Project A
  • add a comment to the issue in Project B

Adding a condition immediately after the trigger to check if the {{issue.project.name}} matches what you expected.  That will prevent issues created in Project B from allowing the rule to proceed.

And as a precaution to rules triggered on Issue Created, I recommend always adding a Re-fetch Issue action immediately after that specific trigger, and before any conditions / other steps.  That trigger can fire so quickly that some issue data may not yet be available.  As a result, conditions and other rule steps may not work as expected.

Kind regards,
Bill

[Alex Hall]

Thanks. I'll try the re-fetch to see if that works. The other solution, while it sounds like it would work, sounds overly complicated when I consider how many rules would have to be created.

[Alex Hall]

The re-fetch did work. Adding the re-fetch before any desired comment additions allowed for the comments to be created regardless of which project the created issues were in.