Pivot table of how many incidents each of my team have worked (updated) by Priority

[incidentguy]

I would like to create a report that is a pivot table showing the number of incidents each of my team has worked on with counts by priority.   This should include any ticket they have updated, by only a count per incident, not per update. ( If Joe Smith updates INC000123 four times, and INC000124 twice the count should only show as 2).   We often end up passing on tickets to others and they don't end up assigned to us and I need to show the number we have worked on by person....

An example would be:

Name	Priority 1	Priority 2	Priority 3
Joe Smith	2	0	5
John Doe	1	2	2
Jack Hammer	0	1	8
Willy Wonka	2	2	4

Can someone show me how to set this up?  

[User179407]

should be something like this. (add filter conditions per your requirement)

[incidentguy]

Thanks, but I need this report for example for the last month.     I tried originally what you said above before I submitted the question here,   but that will only show me things currently assigned to that user, but if they worked on a ticket for 6 hours and handed it over to someone on the next shift that the ticket is was assigned to next, that will not show my team members count.   The same thing with the assignment group, it only filters on the current assignment group.  

I have a team of incident managers and they assign out these tickets to the person who resolved it or owned the causal CI so the person that the ticket ends up assigned to is always different than one of them.     Sometimes they work on a ticket for say 5 hours and the next incident manager works on it for 2 hours until it is resolved and then the ticket get assigned to the group and person that fixed it.  

Given that, any other ideas?

[Michael Fry1]

You can build your report on the incident_metric table with conditions: Definition is Assigned to Duration:

[oscarb]

While very elegant, this solution has two problems.

1. This will only report on updates of users that the ticket was actually assigned to.   Team members while helping each other out on an incident may update the work notes while the ticket is actually assigned to another team member and this will not capture that.     I am still in search of a solution to deal with that.
2. If the ticket is assigned away form the person and then back to them at any point during the incident, it will be counted twice.   To avoid this you can change aggregation to Count Distinct, as I show below.