Exclude ticket tags

완료

21 댓글

  • 공식 댓글
    Vincent Dollet
    Zendesk Product Manager

    Dear all,

    Thank you for your feedback. We have released two new analytics functions, which will make it simpler for you and your teams to report on your tags:

    • INCLUDES_ANY([Ticket tags], "tag1", "tag2") will return TRUE for any ticket that includes either "tag1" or "tag2"
    • INCLUDES_ALL([Ticket tags], "tag1", "tag2") will return TRUE for any ticket that includes both "tag1" and "tag2"

    And by adding a "NOT" logical operator, you'll be able exclude tickets that have any of these tags, or exclude tickets that have neither of these tags.

    You can read more information here.

    Kind regards

    Vincent

  • Greer Davis

    It's not useful to have reports that include everything that's closed_by_merge...most of our clients write in via email and don't bother with threading so we do a lot of merging. Many of my queries are a bit pointless unless we can exclude those tickets.

    6
  • Predintha Jayasinghe

    +1 - We can't really use Explore if we can't exclude merged tickets. Is there another way to exclude merged tickets other than using the Tag? This is very important for our performance indicators.

    4
  • Alex Gillum-Webb

    +1. I'm trying to remove merged tickets for performance reports. Was baffled as to why my exclude filter 'closed_by_merge' was not working, then I saw this post.

    Can we get an update from Zendesk on this?

     

     

     

    3
  • Justin Federico

    +1

    I am confused about what the Tag Filter is supposed to do. It does not seem usable as it is now.

    2
  • Mirjam Happel

    Same here. This needs to be fixed. I just commented on another article. But how the tag filter is set up now (as a list of unique tag combinations) it is useless and a show stopper for us. Including also does not seem to work for us.

    2
  • Stacia Tucker

    +1 this is a must

    1
  • Chris Bulin
    Community Moderator

    @mirjam I had that happen initially too, and creating a new dataset fixed the tag combos. The underlying problem still remains that excluding tags is really broken. But at least you'll be able to use them for inclusions.

    1
  • Hillary Latham
    Community Moderator

    Agreed, I cannot filter out closed by merge tickets.  I'm currently having an issue (I have an open ticket about it) where one of my customers uses Zendesk too and replies to their own ticket comes in as a new ticket for us, so we end up with many merges for tickets.  Without filtering these merged tickets out, my numbers are inflated.

    1
  • Nir Melamed

    Dear Zendesk team, any thought on this issue? will it be fixed soon? 

    Like others have said, it is a given functionality that my Repots are counting on - and not useable!

    Why all these workarounds? please handle our request here as Zendesk customer

    Thanks

    1
  • Marco Orsenigo

    Zendesk team .... 11 month to fix a bug ?? Please give us an exact date to fix this easy function. ins't it  ? 

    1
  • Hitesh Goenka

    Any update on this?

    We really need to exclude the merged tickets in Explore analytics. So, we may get unique tickets in the data.

    1
  • Eugene Orman
    Zendesk Product Manager

    Hitesh Goenka

    The tag reporting feature was implemented and is available to all customers now. You can use the INCLUDES functions to exclude the ticket tags. This article provides some examples: Reporting with tags.

    1
  • Patrick Bu Jonassen

    +1

    0
  • Chris Bulin
    Community Moderator

    This is particularly true for ticket fields that are based on multi-select.

    0
  • Khajik Khajadourian

    This is a must need fix. 

    0
  • Justin Federico

    I created a new dataset as described and this did fix the issue with the tag filter but this is still only useful for inclusions.

    Is creating a new dataset going to be a common occurrence as a workaround for these types of issues? Will I have to continuously recreate my queries using the new, working dataset?

    0
  • sondre pedersen

    A workaround i do for the time being is to create a hidden field which states whether or not ticket was closed by merge by using Triggers based on the Ticket Tag, one trigger which fills out the field and one that removes it (just in case).

    Then, filtering in Explore based on this field instead of the Tag.

    0
  • Chris Bulin
    Community Moderator

    Justin Federico sadly tags that are part of a large dataset (like merge tag compared to all tickets on your account) are not working well in calculated metrics either.

    When I contacted support about it they told me not to use tags in calculated metrics unless you can significantly restrict the data that it is being applied to, "When a tag is used in a metric, Explore tries to search over all possible tag combinations of all the tickets in scope. With multiple tags and a big ticket scope, this hits a lot of query limits very fast. In order to make the query run currently it is suggested that you restrict the time frame of the query more tightly. Also, instead of including your tags in the calculated metric the query will handle it a lot better if you just pulled Ticket ID and then put those tags in the filter section as Ticket Tag = "exampletag" ".

    Fun times!

    0
  • Hillary Latham
    Community Moderator

    Thanks Justin Federico.  Helpful.  I think I can possibly get what I need, I just have to rework a lot of queries depending on the current metric being used (i.e. the tickets created in past 7 days), etc.

    0

댓글을 남기려면 로그인하세요.

Zendesk 제공