Enable Cross-Project Automation Permissions

As users, some of the individuals I support are working to use Jira Project Automation to simplify software deployment that is managed across a suite of modules for a monolithic application platform.

In order for automation rules to work cross-project, their scope must be made either multi-project or global, both of which remove the ability (because of global scope) for project admins to made edits/improvements to their automation rules.

I would propose a solution that allows for project admins to have access to a means of managing cross-project automation, either via the automation owner defining the available scope but retaining editorial permission (e.g. the rule becomes available, but must be approved by project owners in multi-project scopes), by adding individual editorial permissions to automation rules, or by looking to a broader solution like adding automation rules to Plans that can enable this kind of cross-project functionality.

This will save a substantial amount of developer and admin time in that rules scopes will not have to be changed repeatedly during the development of complex automation rules, and will return the ability to manage their own projects and content back to the development teams who operate in these cross-project teams.