Active Incidents with all subtask closed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello colleagues i need some advices regarding this request , i was tryng to configured in zurick version platform analytics , to get all inicdent that our active and not resolved and the subtask are all closed but for now i have try several scenarios and none of them work,
1- i have tried base table incident here ii just use the the condition is active is true , and state is not resolved , and assignment group is x. then i use the related conditon to get into greater then one incident task-->parent
then here i use state is closed and resoltuion code is not duplicted,
here the results is partylly true , because i get incident that our active but in the subtask i getting as long is one closed then i get this ticket but i need the subtask list to be all closed ..
2- second round then i try to give a flip to the logic same base inicdent table same conditions thne in related list condition i have put none incident task --> parent , then in the condition isaid open, work in progress , pending , resolution code not duplicated , so iwas think i might get all closed incident with this, what happens is the i get all active tickets but the list of sibtask they dont conain none and some i get all closed , so here is also partially true because i get some of the incident with all subtask closed but also get some incident that have now.. hopelly someone know something similar and can tell me something. Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @licmartinez
refer: View Incidents where all tasks are closed
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @licmartinez ,
The challenge is that Related List Conditions evaluate whether at least one related record matches (or doesn't match) the criteria—they don't evaluate whether all related records satisfy a condition.
A better approach is to identify incidents where no related Incident Tasks are in a non-closed state. For example:
Base conditions:
Active = true
State != Resolved
Assignment Group = your group
Related List Condition:
None → Incident Task → Parent
State is not one of the closed states (or Active = true)
This returns incidents that have no open Incident Tasks, which effectively means all existing tasks are closed (or there are no tasks).
If Platform Analytics still doesn't produce the expected results, consider creating a database view or a scripted indicator to calculate whether all child Incident Tasks are closed, as this type of "all children meet a condition" logic isn't directly supported by standard related list conditions.