- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2014 07:49 AM
We're planning to enhance the resolution code for our Incident management. I wanted to see what kind of resolution codes you're using so that it helps you better on Incident trending and resource utilization.
For ex: I am more thinking like hierarchical closure codes for us. I have come up something like this
- Application/Software
- defect raised
- Existing Defect
- Restart / Reboot
- Configuration changes
- new functionality / enhancement
Any thoughts / suggestions or samples to share what you do on your side?
Thanks again
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2014 09:36 AM
I attached our layout, however I do 100% agree with rfedoruk. If you do not have a level of accountability, and management is not actively reporting off the close codes, the hierarchical method can quickly generate bad data.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2017 10:42 AM
You can use Informational only or Training Opportunity as a cause code for incidents like these.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2020 09:19 AM
hello
We are currently looking at our SN implementation and this is something we are looking at
ie to add a "reason" when closing incidents, so we can run trend analysis to "spot problems"
To do this , did you make some config or did you have to add customisations
We are trying to avoid customisations, as this can impact release upgrades
thanks
sarah
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2020 06:57 AM
OOB there's a closure code choice list.