As we implement out our Jira Enterprise, we are finding we need to have automation hooked to certain project.  This can be achieved, but when we are talking about 600+ projects this can be tedious.

It would be great if in the automation rules you could select Project Category as an option of where to apply this too.  Example of our config:

• We will have 1,000+ projects all categorized:
  • Benefit Client Operations
  • Non Benefit Client Operations
  • Shared Service
  • Support
  • Other
• We have automation that has to apply to just the Benefit Client Operations, which will be the largest chunk of our categories.  

Just due to anticipated volume in our environment, we want to be as proactive as possible with any automation and integration into our Jira environments.  Even though we setup the rule and it won't necessarily meet the criteria for one of the other project category (maybe not the field condition or the issue type condition), it doesn't make sense to be running it let's say 20k times a day just to fail the condition when we know it shouldn't be on the project (at this point with the choices, it's just easiest to set this up as Global because we don't want to chose 600+ projects for it to target).