I have checked some examples and it seems to work! 🙂 In addition, the other count has decreased from 530 to 379 and it fits for me to still have a big number, but the decrease thinking of all the duplicated events between parent tasks and sub tasks. Can you please explain me a little bit what those functions do? To learn more. Thank you! ... View more

Hi, I hope this fits the request, not sure if I'm adding too short info. These are the values for the example, anonymised enough but with useful values. row # ticket_number task_number parent_task sub_task Product Provider to_team 1 tic3624 tic3624.1.2 tic3624.1 tic3624.1.2 A a bcn 2 tic3624 tic3624.1.1 tic3624.1 tic3624.1.1 B  b   3 tic3624 tic3624.1 tic3624.1   Other     4 tic3625 tic3625.1 tic3625.1   A a   5 tic3626 tic3626.1 tic3626.1   Other     6 tic3626 tic3626.1 tic3626.1 tic3626.1.1 A   bcn 7 tic3627 tic3627.1 tic3627.1   Other       I have a long eval checking both Provider and to_team fields, always giving priority to the provider, but checking the team in case there's a subtask delegated. Then, in the example above, if only the Other (rows 3 & 5) should not be counted but because there are subtask. At the end, the Other is there in case there are tickets that can not be identified (i.e. last row) Thanks ... View more

Hello, I tried and in this particular case it works, but not for all the cases. I have discovered that some of them are missing the Provider field but they should be counted, hence I need to use another field that indicates to which team we have send the case. Then the issue is when the Product is other for a parent task that has subtask with a Provider or a destination team.   This is getting too much complicated maybe 😞 ... View more

Hi, These are the values for the example, anonymised enough but with useful values. ticket_number task_number parent_task sub_task Product Provider tic3624 tic3624.1.2 tic3624.1 tic3624.1.2 A a tic3624 tic3624.1.1 tic3624.1 tic3624.1.1 B  b tic3624 tic3624.1 tic3624.1   Other     All three events have the same ticket_number and same parent_task. And this will happen with other cases like this one. It gives the count of 1 ticket for Product A, one ticket for Product B and one ticket for Other, but this last part not being completely true. If we look at the event is correct, because there's no Provider, but it was something we delegated. Filtering out all the events without sub_task will not work because some of the task are not delegated that need to be counted. ... View more

The number of events inter related is something I cannot say because it depends on if one ticket has been delegated or not. Selected Fields Interesting Fields index 24 Product 19 Service 100+ created_at 100+ from_team_name 12 from_team_type 3 Provider 38 redirection_type 4 sub_task 100+ task_number 100+ ticket_number 100+ urgency 5 This are the fields I'm using to find out how many tickets we have handled for each Product looking at Provider . I remove duplicates with | dedup ticket_number,Product because one ticket can have more than one product related. In the example above I'm counting three events with the same ticket number but with three different products one being "Other", which can make sense. The issue is that one of those events is the parent task that appears in Other because in that event the Provider field is empty. In those situations I would like to skip the parent task as it's not true there's no identified product, its subtask has one, but it' not populated in the event for the parent task.   What I was thinking at the beginning is to use one of the subtask value Provider and bring that to the parent task event. Then, when executing the dedup it wouldn't be counted because two events will have the same Product and Provider. However, I don't know how to actually build a subsearch for that.   ... View more