Halo Integration NextTicket Filter Improvements
product review
E
Ethan Slagle
We would like to have the ability to use Grouping statements in the filters in order to make use of the “or” statements. This is currently not available for Halo like it is with some of the other tools such as Connectwise. We would also like to have the ability to use "not in" for the rules within NextTicket.
For example, for statuses within Halo we only have the option of “in” which will force us to select around 10-15 statuses, whereas if we had “not in” we would only need to select a few. This feature looks like it's already in place for some of the other ticket handling tools.
Log In
Micus
Hi Ethan Slagle, dev team has get back: status "not in" is not supported by Halo API, so NT can not send this to Halo to filter tickets. If you want to filter tickets by it, NT would use the data synced in our db, which may not be the latest and cause inaccurancy.
This post was marked as
product review
Micus
Hi Ethan Slagle, the fields and operators are sent to Halo to filter tickets, so only the ones Halo accepts can be used. I will take it to our dev team for further information.
Thanks!