- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2017 02:14 AM
User wants to see all Incidents transferred from any of his groups back to the Helpdesk, where they get closed.
I'm filtering on Assignment Group metric definition, but results are understandably duplicated (multiple Updated(mi_sys_updated_on) ) values.
Can reporting just pull the latest (MAX?) Updated record, so we only get one record per ticket?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-23-2017 05:05 PM
Hey Russ, sorry you haven't gotten a reply to this yet. I was just browsing old questions and thought I'd have a crack at it. Hopefully you haven't gone away totally yet.
I actually answered a question very similar to this, here's the answer. What you can do is set up this exact same metric, and run your report on the incident metric table such that the definition is Incident Touched, the value is your group's name, and the assignment group is the help desk. That would effectively give you a list of all tickets (without duplicates) that were in your queue at some point and that ultimately ended up at the Help Desk.
If you want a metric to measure tickets that were actually transferred directly from your group to the Help Desk, even if the Help Desk transferred it somewhere else after that, that might be a bit more difficult, but doable. The thing is, metrics don't capture the previous value of the field, only the current value of the field. What you'd probably have to do is actually have a dummy script in the metric definition, and use a business rule instead to create the metric instances based on your criteria. Let me know if you have that kind of specific need, and I'll try to help out.
Otherwise, try the script linked above, and let me know how it goes.
Hope this helps,
--Dennis R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-23-2017 05:05 PM
Hey Russ, sorry you haven't gotten a reply to this yet. I was just browsing old questions and thought I'd have a crack at it. Hopefully you haven't gone away totally yet.
I actually answered a question very similar to this, here's the answer. What you can do is set up this exact same metric, and run your report on the incident metric table such that the definition is Incident Touched, the value is your group's name, and the assignment group is the help desk. That would effectively give you a list of all tickets (without duplicates) that were in your queue at some point and that ultimately ended up at the Help Desk.
If you want a metric to measure tickets that were actually transferred directly from your group to the Help Desk, even if the Help Desk transferred it somewhere else after that, that might be a bit more difficult, but doable. The thing is, metrics don't capture the previous value of the field, only the current value of the field. What you'd probably have to do is actually have a dummy script in the metric definition, and use a business rule instead to create the metric instances based on your criteria. Let me know if you have that kind of specific need, and I'll try to help out.
Otherwise, try the script linked above, and let me know how it goes.
Hope this helps,
--Dennis R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2017 02:34 AM
Dennis - thanks, that worked just as I wanted.
The retrospective background script only ran for a few tickets on our DEV system, but thats not too important... main thing is I got what I wanted.
thanks again!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-22-2017 08:38 AM
Hi Dennis,
May I know the best practice of scheduling report on Incident Metrics table, like how much frequency we can set to fetch data from Incident metrics table ?
ex: every 2 hours or 4hours or 6 hours or 12 hours
Kindly share your comments.
Regards,
Narendran
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-02-2023 07:20 AM
Hi Dennis,
I am working on something similar. I want to do this on sc_task. Basically, we want to calculate the number of tasks going through ServiceDesk.
1. Task landed on ServiceDesk queue and got resolved
2. Task landed on ServiceDesk queue and re-assigned to another team and then got resolved.
We need to track both the task count. Is there a way to create a report for this one?
Thanks in advance