Recent searches
No recent searches
Number of escalations from one group to another
Answered
Posted Aug 27, 2019
Hi
I've been trying to create a report showing how many tickets have been escalated from Tier 2 to Tier 3 with no luck. So far I've tried by creating a custom metric as well as using the Group Reassignment metic but they are either not working or given me the wrong results. I'm using the Ticket Updates dataset.
My custom metric looks like this:
IF ([Changes - Field name]="Group" AND [Changes - New value] = "Tier 3"
AND [Changes - Previous value] = "Tier 2")
THEN [Ticket ID]
ENDIF
0
8
8 comments
Official
Amber Ring
Hi Marie-Cathrine,
The group changes actually uses the group id instead of the group name! So, you would have to use [Changes - Field name] = "group_id", and use the group ids for the [Changes - New value] and [Changes - Previous value].
Hope that helps! Thank you!
0
Trevor Kanaya
Is there any way to render the name of the previous group at all? We're making a query for which teams our escalations are coming from. If we use "group_id", our query looks like this and is not useful:
But as mentioned above, "group_name" isn't an option, so is there any workaround for this? Another user asked the same question and there was never a response so hoping something's possible, otherwise there's no way to run a report to get the information we want in Explore.
Even if we could even just manually re-label the columns once the query is finished, I would be willing to do that although it seems to be the option to display by name should just be a default attribute. In any case, manually relabelling doesn't seem to be an option so any thoughts would be appreciated.
Cheers,
0
Stephen Belleau
@... Indeed there is a workaround for you. You can use the SWITCH & CASE functions to rename each group ID to its name.
You will need to list all groups in your instance within this custom attribute, so it's going to take some maintenance if you add new groups. Here is an example to get you started:
0
Trevor Kanaya
Oh snap! Yeah that'll work for me. It's not ideal but it will do just fine for now. Thank you for this!
0
Kai Schmitte
Hi all,
will this solution be possible with using a placeholder?
Currently I would need one calculated metric per group to show the tickets that are escalated to each group. Means instead of using "group_id = "xyz" I would use something like "Ticket group" = [Ticket group]:
IF ([Changes - Field name] = "Ticket Group" AND [Changes - New value] = [Ticket Group]) THEN
[Ticket ID]
ENDIF
Which would allow building an overview over the tickets escalated into all views.
0
Marie-Cathrine
Hi Kai,
You might be able to do something where you compare the previous value to the new value. But could you maybe elaborate a bit on what kind of report you want to create? Then I can better guide you in the right direction of how you might be able to create one combined metric instead of multiple.
#helpsome regards,
Marie-Cathrine Sørensen
Developer @ helphouse.io
0
Kai Schmitte
Hi Marie-Catherine,
essentially it is quite simple: There are 3 groups- T1, T2 and T3. Escalations go from T1 to T2 to T3. Additionally tickets are created in T1 and T3. Now I would like to see how the workload is in T2 (only escalations into this group) and how the workload is in T3 (Escalations into the group + new tickets).
I could use the recipe above to build one metric for each group (T1, T2 and T3). More nice would be to have the metric built in a way that allows me to build one query that shows all 3 groups at once. And allows filtering on groups in case we add more groups or only want to show a specific one.
Main report should be: escalations into a group by month
0
Marie-Cathrine
Hi Kai,
Sorry for the late response. Even though you might have found a solution in the meantime, I would still like to give you my input on how you can solve this issue and create a report along the lines of what you are looking for.
Solution 1
The first solution is to create an attribute instead of a metric. This attribute allows you to divide the Updates metric into different groups (in this case escalations from one group to another). This one is similar to the metric but allows you to combine different scenarios in one. Therefore, this solution also requires you to manually keep it up to date with new groups.
The recipe for this solution would be:
You should now have a report similar to this:
The attribute created in this solution can also be used for filtering.
Solution 2
This solution is more dynamic and doesn't require as much maintenance as solution 1, but it might also show escalations that you might not want to see in the report (e.g. escalations to T2 that come from a group that isn't T1).
The recipe for this solution would be:
You should now have a report similar to this:
This one can be filtered using the New value attribute.
#helpsome regards,
Marie-Cathrine Sørensen
Developer @ helphouse.io
2