I'm working on some cross project automations.
When new issue is created in Project A:
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
Has the community dealt with this? Any suggestions to work arounds?
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:
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.