OR and IS NOT Logic for Ticket Automation Conditions

Right now, ticket automation conditions only support AND logic. This makes it clunky to build automations where any one of several values should trigger the same action.

For example, I want an automation that fires when a client replies to a ticket AND the status is one of: Solved, Waiting on Client, Hold, Waiting on Parts, or Scheduled. Since there's no OR option, I have to build five separate automations, one per status, just to get the same result.

If thre was IS NOT logic I could build it the reverse way. I'd like to say "if ticket is unread AND status is NOT New" but instead I'd have to list out every status that isn't New.

Ask: Add support for OR conditions (and ideally a "does not equal" or "is not" operator) within a single automation rule. Something like a condition group where I can select multiple values for one field would solve both cases above and cut down on a lot of duplicate automations.

This would make automations way easier to maintain since one rule change wouldn't mean updating five near-identical copies.