Issue Summary

The current functionality of Global Automation rules in Jira prevents users from effectively restricting editing access to specific admins. Despite selecting specific admins, other Jira Administrators can still edit the rule. It is crucial for users to have control over who can edit specific rules, and they expect that the configuration for Global Automation rules can override the general access configuration. Otherwise, the "Who can edit this rule?" feature in Global Automations becomes ineffective.

Steps to Reproduce

1. Create a Global Automation rule.
2. In the rule details, change the "Who can edit this rule?" value to "Specific admins".
3. Add any admin to the "Search for admins" list.
4. Save the rule and apply changes.
5. Access the Global Automation with another admin (not added in step 3), and observe that you can edit the rule instead of it being "READ-ONLY".

Expected Results

Admins who are not added to the list of specific admins authorized to edit the rule should see the rule as "READ-ONLY" and not be able to edit it.

Actual Results

Any Jira Administrator, including users added to site-admin, jira-admin-instance, jira-administrators, etc., can edit the rule, regardless of whether they are added to the specific admin list. While this behavior aligns with the documentation, it is not intuitive and renders the ability to restrict access to Global Automation rules useless. This issue is closely related to the new user management experience.

Workaround

Currently, there is no known workaround for this behavior. We will provide a workaround here as soon as it becomes available.