Issue Summary

Project administrators would see Automation rule labels as unused if there are no rules assigned to it within the current project.
This would happen even if the same label is assigned to rules from other projects.

With the bug JIRAAUTOSERVER-299 resolved on Automation 8.1.2, these labels can be removed with a misleading information that they are not used.

Steps to Reproduce

1. Install a vanilla instance of Jira Software Data Center.
   • This was validated on Jira version 9.14.0.
   • This has been an bug for quite some time, but with JIRAAUTOSERVER-299 it's allowing for a destructive action.
2. Create two users to be assigned a project administrators later.
   • i.e. padmin001 and padmin002.
     
3. Create project AUTO1 and assign padmin001 as a project administrator.
4. Create project AUTO2 and assign padmin002 as a project administrator.
5. Authenticate to Jira as padmin001 user.
6. Access the settings of project AUTO1 and go to Automation.
7. Click on Add label and create a new label.
8. Create a couple of rules and assign the new label to them.
   
9. Authenticate to Jira as padmin002 user.
10. Access the settings of project AUTO2 and go to Automation.
11. Check the label portion from the Automation admin page.

Expected Results

The label create by padmin001 user does not appear as unused and the padmin002 is unable to remove it.

Actual Results

The label create by padmin001 user appears as unused and padmin002 can remove it.
Choosing delete shows that "Deleting this label will not affect any rules" even though it would.


Since Automation rule labels are global, the label is gone on the entire instance even though there were rules assigned to it (rules are not affected).

Workaround

As a workaround, we suggest that you login using the Global Admin permissions as Jira Admin and navigate to ⚙ > System > Automation rules and check for the labels here. If any labels are displayed as Unused here, then you can delete them from here.