suggestion to detect scope errors in rules

[Bill Sheboy]

Greetings, community!

TL;DR: what do you think of rules raising an error when attempting to access or edit an issue outside the rule's scope?

Project scope can lead to interesting problems for automation rules.  With the packaging changes to global rule execution, customers now have more flexibility to solve these problems...but only if we can see there is a problem.

Rules in one project scope can create (or clone) issues into other projects, but they cannot see or edit them otherwise.  For example, when branching to a newly created issue in a different project to perform an edit / link, the audit log will show no branch matches and not raise an error for the root cause of the problem: scope mismatch.

Detection of a scope mismatch could sometimes be seen when the rule is created / edited, and other times as issues are accessed during execution.  Raising an error will improve customer understanding of rule scoping and likely prevent unknown / mysterious errors for rules that seemed to succeed.

Thanks!

[Mauricio Heberle]

We definitely need a better audit log in automations.