Issue Summary

If a user that is not a product/site admin owns an automation rule that is global/scoped to multiple project, the email notifications for rule failures will only link to the global automation URL, which the non-admin cannot access. 

For example, the email template for a failed rule looks like the following:

The automation rule <ruleName> just failed with an error on your Jira instance (https://<siteName>.atlassian.net)

Check the audit log for more details in the automation admin section (https://<siteName>.atlassian.net/plugins/servlet/ac/com.codebarrel.addons.automation/cb-jira-automation-rules*/rule/<ruleID>/audit-log?auditLogId=<auditLogId>)

Ideally, it would be best if the rule owner was directed to where the rule was originally created. The URL Path for a rule viewed within a project looks like the following: 

https://<siteName>.atlassian.net/jira/software/c/projects/<projectKey>/settings/automate#/rule/<ruleID>

Steps to Reproduce

1. As user with project admin permissions, but without site/product admin permissions, create an automation rule within a project
2. Add multiple projects to the rule scope
3. Have the rule fail (this will be hard to forcefully reproduce), resulting in the email linking the rule owner to the global automation rule URL

Expected Results

The rule owner will receive an email linking them to the rule they manage

Actual Results

The rule owner receives an email linking them to the global automation page that they cannot access 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available