Allow "Hours since" conditions in ANY conditions list for Views

We're in the same boat and at a complete loss, would love to see this be able to happen.

We want a view to show all tickets within a certain breach window (e.g. less than three hours till breach) but also still show tickets in that view if they have already breached as well. Unfortunately this is impossible since "Hours until breach" must be an ALL condition and once the ticket breaches, it no longer technically has a time until breach number since the breach event has passed. The effect it's having is that now after the ticket breaches, it vanishes from the view. Any potential solution to this is cumbersome and has downsides:

1. Use an automation to tag tickets once they hit the breach window and remain tagged after breach, therefore allowing us to remove the "Hours until..." condition from the view and just pull by tag. Downside is that if we use an automation, since they only run once/hour, there's the potential for the tag to not be applied for a full hour after the ticket should be in the countdown window if it misses its first opportunity to run.
2. Use the API to tag these tickets in real time. For high-volume Zendesk users who occasionally hit the API rate limit momentarily, this runs the risk of having some tickets miss getting tagged.

We can't use any alternative hours logic (e.g. hours since creation, hours since update, due date) because in all those instances there will be a cutoff for which we also want to pull tickets after that cutoff as well, no matter where that clock is ticking from.

My organization would definitely benefit from this feature. We have a number of tickets where the ticket might get picked up by a resource outside of our customers time zone and having a view that could display priority tickets and tickets that have been updated within a certain number of hours would let us focus on prioritizing urgent tickets as well as see if customers might be attempting to escalate an issue that has not yet been flagged as a priority ticket.

This lack of an hours since updated being a “meets any” condition requires us to have multiple views instead of a combined view.

I just want to add that we also have users requesting this functionality right now. This would be very helpful for us and our users.

I have the same issue and need a solution now.

The only solution I can think of is using a combination of an automation/automations, that add a “over_24_hours_waiting” tag to all tickets that are in status new, open or on-hold for at least 24 hours. And a trigger that removes that tag in case the status changes to NOT one of the three stati.

Only then I could view those tickets in a view I guess.

I'd also like to see this implemented for automation with a restriction to the IS condition instead of not available at all as it shouldn't be able to loop with this limitation and would be useful for streamlining parts of our process. 

I would consider this a handy feature:

It allows you to override any filter specified in the ALL conditions section.

For example:

I may have added a filter to not show tickets with a tag (e.g. call-scheduled) in ALL conditions. However, if a user replies, I would like this to be overridden (maybe some action has to be taken?) and the ticket to reappear in the view.