Exclude ticket tags

9 Comments

  • Patrick Bu Jonassen
    Comment actions Permalink

    +1

    0
  • Chris Bulin
    Comment actions Permalink

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

    0
  • Khajik
    Comment actions Permalink

    This is a must need fix. 

    0
  • Justin Federico
    Comment actions Permalink

    +1

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

    1
  • Stacia Tucker
    Comment actions Permalink

    +1 this is a must

    0
  • Mirjam Happel
    Comment actions Permalink

    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.

    1
  • Chris Bulin
    Comment actions Permalink

    @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
    Comment actions Permalink

    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
    Comment actions Permalink

    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.

    0

Please sign in to leave a comment.

Powered by Zendesk