Explore User Group Filtering
It's seems that in explore (same as in insights) we still don't have the ability to filter based on a users group. I know we can filter based on ticket group, but I'm looking more at a group of users rather than what type of ticket they are looking at. Currently all we can do is add each user 1 by 1 to a filter of a report, multiply that by however many reports you have and by however many groups you have, thats in INCREDIBLY time consuming process.
We need to be able to filter by user group in examples like...
- Updater is a member of "XYZ" Group.
- Assignee is a member of "XYZ" Group.
- Requester is not a member of "XYZ" group.
Doing this based on a ticket group is not sufficient because we have many groups that respond and work in multiple areas, so if I want to report on our "Vetting" team - they may be interacting with other groups on tickets, and I can't make a report where I look at the # of updates from users on the vetting team for the last week, organized by user. At least not without singling out each user, but this creates a huge strain creating and updating the reporting based on team changes/turnover/etc.
Also, if we were able to do this we could cut down on the total number of reports by adding a dropdown filter to a dashboard to select which user group someone wants to report on. So the same "Ticket Updates" report from my example above could be used to serve multiple teams.
Unless I'm missing something and you can show me how to do this, I haven't been able to figure out a way myself, or in the community or KBS articles.
I think I might be able to hack a solution using tags, but that seems like an unnecessary burden given that the group information already exists, and we would essentially have to maintain groups AND tag groups to make this work, when just maintaining groups should be enough.
We should also be able to do this with custom Agent Roles.
Seems like such an easy field to report off of. Its hard to explain to our managers why a report shows a user belongs to multiple groups because its pulling the user group from the ticket not the user
This is such a weird thing to be missing and required me to build really stupid elaborate tagging schemas to basically track groups in a way that allowed me to report on them in explore. It also is confusing for non-technical people who don't understand why you can't do this thing that seems very reasonable.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.