Issue Summary

Project admins, who are not product admins, cannot update Multi-Project Automation rules even when they are project admins to all the projects covered in the automation rule.

When the project admin goes to update the rule, they will see the rule's configuration but will be in 'Read-Only'.

Expected Results

If a user is a project admin of all the projects of a Multi-Scope Automation rule, they will be able to update the rule via Project Settings > Automation.

Actual Results

When the project admin goes to Project Settings > Automation and selects the multi-project rule, they are only able to access it in read-only mode.

Steps to Reproduce

1. Create a secondary account that is not a jira-admin or site-admin, but is a project admin for 2 company-managed projects (need* Administer Projects* and Browse Projects permissions)
2. Create an Automation Rule with Multi-Project Scope, scoped out for the 2 CMP projects
3. For Who can edit this rule select Specific admins and select the secondary account
4. Ensure that in Global automation > ... *> *Global configuration that the user is in one of the groups to Allow project administrators to manage project rules
5. Log in with the secondary account
6. Navigate to one of the projects and go to Project Settings > Automation and try to edit the automation rule.
7. It will say “READ-ONLY” at the top despite having access

By Comparison:

1. Change the rule to Single Project Scope for one of the Projects and Save it
2. As the Secondary user, try to edit the rule again
3. you will now be able to update it.
   (edited)

Other requests around permissions: https://jira.atlassian.com/browse/AUTO-620

Workaround

Since project admins can update Single Project Automation rules - make a Single Project rule for each project in the Multi-Project rule