- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2024 08:08 AM
Utah Patch 5
We have quite a few CIs that with an operational status of non-operational and an install status of retired; they will no longer be updated. They are currently being flagged as stale. We do not want to delete them and lose that information. Is there a way to filter out these CIs so that they don't impact the staleness metric or is that not a good idea?
Thank you
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2024 08:29 AM
Hi @mah1 You can configure "Health Inclusion Rule" for those class which you dont want to fall under stale, also you can apply condition on it so based on that it will filter it out and it will not create stale tasks.
Doc link for further details.
Hope it will help you.
Thanks,
Harsh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2024 08:29 AM
Hi @mah1 You can configure "Health Inclusion Rule" for those class which you dont want to fall under stale, also you can apply condition on it so based on that it will filter it out and it will not create stale tasks.
Doc link for further details.
Hope it will help you.
Thanks,
Harsh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2024 09:36 AM
ok, thank you