- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
MTTR calculation by excluding onhold state , OOB indicator having [[Summed duration of resolved incidents]] / [[Number of resolved incidents]] its include onhold state so how to exclude and calculate MTTR
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Yes :). It'll give you better control as you can then be more granular in defining what is and isn't included in your MTTR KPI, without needing to manage a lengthy script. The logic is managed within each SLA resolution definition
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
see this link which talks about custom script, see if that helps you in calculation in your PA indicator
Create metric definition to calculate total time taken excluding on hold duration
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
i will create a metric definition by excluding the onhold state , then how to calculate MTTR, via report or you saying to create a custom field to store the value
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Please check that link and there is an approach
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Jeya,
Rather than creating a new metric, have you considered using task_sla as your indicator? Assuming you have SLAs already, you can leverage the SLAs with a type of resolution to calculate the overall duration.
