Exclude ticket tags

16 댓글

  • Patrick Bu Jonassen
    댓글 작업 고유 링크

    +1

    0
  • Chris Bulin
    댓글 작업 고유 링크

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

    0
  • Khajik
    댓글 작업 고유 링크

    This is a must need fix. 

    0
  • 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
  • Stacia Tucker
    댓글 작업 고유 링크

    +1 this is a must

    1
  • 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
  • Chris Bulin
    댓글 작업 고유 링크

    @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
  • 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
  • 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.

    4
  • 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.

    3
  • 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
  • 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?

     

     

     

    2
  • Hillary Latham
    댓글 작업 고유 링크

    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.

    0
  • Chris Bulin
    댓글 작업 고유 링크

    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
    댓글 작업 고유 링크

    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 제공