What is the difference between "meet all" and "meet any" conditions?

Return to top


  • Joshua Bentley

    Views seems to be handled differently than Triggers and Automations because it's not a business rule.

    The verbiage for Views is "Tickets can meet any of these conditions to appear in the view" versus the verbiage for Triggers/Automations which just says "Meet ANY of the following conditions".

    When I create a view, it seems to me that the Any list is more like a suggestion list. Example: I have in ALL the following - Assignee: "-" and Group: "Support". And it doesn't seem to matter how many conditions I have in the ANY section, all tickets unassigned and in the Support group will show up in the view. As if it's meeting only the ALL conditions.

    As if the view can include those, but it doesn't have to. LOL

  • Kharlo Reboja
    Zendesk Customer Care

    Hi Joshua,

    Thanks for reaching out! The different condition sets within triggers refer to the operators that apply between each condition.

    Conditions in meet all of the following conditions utilize the and operator. This means that each condition in this section must be true for a ticket in order for the trigger to fire. For example, I have the following conditions in the all condition set:

    Ticket | Is | Created
    Channel | Is | Email
    Organization | Is | Test org

    For the trigger to perform any action on a ticket, the ticket must be created, sent in as an email, and the organization associated with the requester must be Test org.

    Conditions in meet any of the following conditions utilize the or operator. This means that at least one condition in this section must be true for a ticket in order for the trigger to fire. For example, I have the following conditions in the any condition set:

    Channel | Is | Chat
    Channel | Is | Email
    Organization | Is | Test org

    For the condition set above, a ticket must either be received as chat or received as an email or the organization on the requester must be Test org, but does not need to match all three.

    The all and the any condition sets can be used in conjunction. When using both, a ticket must match every condition in the all section, plus at least one of the conditions in the any section. If there is only a single condition in the any section, it must be true. The OR does not apply between conditions in the separate condition sets.

    Kharlo | Customer Advocate

  • Joshua Bentley

    Thanks for the reply @.... It doesn't seem to answer my issue, however. Would it be helpful for me to provide screenshots so you can see the difference in results between Triggers and Views?

  • Qasa

    Hi! Is there any way to have "meet none" conditions? 

  • Cheeny Aban
    Zendesk Customer Care

    Hi Mattia,

    You can achieve the same by adding the condition "is not" under the MEET ALL conditions. This means that each condition in the section must be false for a ticket in order for the trigger to fire.


  • Qasa

    Hi Cheeny! 

    I am looking for a way to trigger a rule if a date parameter "is NOT within the previous" X days - it only seems possible to choose "is within previous". Do you know of any workaround? This would be incredibly helpful! 

  • Jimmy Rufo

    It would be nice if we could implement an OR sub condition within one of the "Meets All" conditions.  For instance, something like below:

    Comment text -> contains the following string -> TextA OR TextB

    As of now, I'd have to create two separate triggers to get this scenario to work, unless I had those text options create individual tags, and then build a trigger on tags.

  • Jake Warren

    Cheeny Aban - Is there a way to be more specific with this logic to where you configure combinations of AND/OR type conditions? So for an example you might have 3 different conditions:

    1. Issue field IS NOT Product Bug
    2. Issue field IS Product Bug
    3. Priority IS Urgent

    I want to put something together where the logic would be: 1 OR (2 AND 3). How would I accomplish this?

  • Dane
    Zendesk Engineering
    Hi Jake, 

    Unfortunately, automations and triggers does not have this capability.
    Would you mind posting your use case to our Feedback on Support topic? We have a template you can copy and use in your post. This is to help get more visibility and votes on the idea. Then, others can share their use cases to further drive demand for that feature. Thanks!

Please sign in to leave a comment.

Powered by Zendesk