- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-04-2024 07:41 AM
I am currently building a dashboard on PA and I need to add two breakdowns: one for reassignment count which is calculated by script and re-open count. I am not able to create those using bucket list as number of re-assignments cannot be predicted. Is there any way to add them as breakdowns?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2024 06:06 AM - edited ‎12-05-2024 06:35 AM
Instead of predicting precision ... "I need a bucket for 1,2,3,4,5,6,7,8,9 ++ ", take inspiration from the AGE buckets.
Age buckets are ranges, with the OOB final range being "90 or above"
ReAssignment and ReOpen don't need precision. Its EASY for stakeholders to agree on comfortable vs uncomfortable ranges.
0-2 Reassignments? That's fine
3-5 Reassignments? Concerning!
6+ Reassignments? What the absolute hell is going on here anyway?!
See? At a certain point you don't care if its 6, 8, or 80. At that point its "just too f---ing many".
Same story for re-opens.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-09-2024 06:12 AM
Wait... the whole point of buckets is to have a breakdown.
Are they really trying to break them down by DISTINCT counts?
Like is someone literally graphing "Incidents with 4 reassignments" as a completely different thing than "Incidents with 5 reassignments"?
You can build reassignment metrics without them being a BREAKDOWN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2024 06:06 AM - edited ‎12-05-2024 06:35 AM
Instead of predicting precision ... "I need a bucket for 1,2,3,4,5,6,7,8,9 ++ ", take inspiration from the AGE buckets.
Age buckets are ranges, with the OOB final range being "90 or above"
ReAssignment and ReOpen don't need precision. Its EASY for stakeholders to agree on comfortable vs uncomfortable ranges.
0-2 Reassignments? That's fine
3-5 Reassignments? Concerning!
6+ Reassignments? What the absolute hell is going on here anyway?!
See? At a certain point you don't care if its 6, 8, or 80. At that point its "just too f---ing many".
Same story for re-opens.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-09-2024 03:51 AM
I already proposed this, however team wants to see actual numbers, not 'bucketed list'. Same way they currently see in general reports. Any other solution without using buckets?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-09-2024 06:12 AM
Wait... the whole point of buckets is to have a breakdown.
Are they really trying to break them down by DISTINCT counts?
Like is someone literally graphing "Incidents with 4 reassignments" as a completely different thing than "Incidents with 5 reassignments"?
You can build reassignment metrics without them being a BREAKDOWN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-10-2024 02:22 AM
They are graphing by increments of one, but I will use buckets and explain why this method is more effective and how important it is to have a plan to reduce the count. Thank you for your assistance.