Multiple AND/OR conditions in Views, Triggers and Automations

+1 here as well. I have just had to create 4 automation tasks to handle 1 thing that I wanted to achieve. 

+1 We have lots of duplicate triggers because it needed many any conditions.

Ie. it fires for this group with any of these phrases but also this group and this group (if we need to adjust the phrases, it will need to be adjusted more than 1 time)

+1 This functionality is essential and missing in the base product.

Hi 1265012788550 we are still considering this a top priority, but we don't have any updates to share at the moment. We are still scoping out what is possible against other priorities. 

In the meantime, I do have a survey up looking for detailed use cases on some of the things we are considering for triggers if you're willing to participate that would be greatly appreciated! 

Hello Bailey Whitaker-Lea, 

I was wondering if you have any updated on this topic. 

Regards

Marta

I am going to have to echo those above. We are currently using just over 280 triggers on our zendesk account. I could cut that number down to under 150 if I could specify groups of activation. Currently I have to have a separate trigger for each group of conditionals.

Those triggers all add the same tag to the ticket, which activates a different trigger which does what we need to the ticket and then removes the activation tag. All of those triggers could be condensed into a single trigger if I could group the conditionals.

+1, this would vastly improve the condition configuration experience and functionality!

Thank you for the very thorough explanation.  That really helps.  

Hi Phil, 

We do state in our product feedback guidelines (pinned at the top of every product feedback topic in the community) as well as in the Community Code of Conduct that our teams do read all of the posts and comments in the community, but cannot respond to everything just due to the sheer volume of comments we receive. (But we love how engaged everyone is!) 

We recognize that responsiveness has been problematic in this space for a long time. To help improve on that experience, we have implemented some new processes and expectations with our product teams this year toward increasing engagement in the community, specifically related to product feedback.

But, the way that product feedback works within this community is not the kind of process where users suggest an idea and it's accepted or rejected in X period of time or responded to at X number of votes. It's meant to be an opportunity for users to discuss challenges or issues or make suggestions, and where product managers can get an understanding of user needs, themes around issues, and bring the information they gain here into the product roadmap and design conversations. 

As far as the request in this thread goes, it's a great example of one where the product manager is reviewing all of the (many) threads and requests related to Views and looking for patterns, where one solution could solve for multiple needs, etc. So they may not be able to go in and comment on each individual idea whether that specific one is getting developed at a specific time, but rather as improvements are made to that area of the product you will likely see several of the issues raised in these forums get resolved over time. 

I hope that clarifies things a bit, and I will reach out to the product manager to see if they do have anything to add here.