- 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
04-24-2014 02:22 PM
This is an interesting approach. We are still using the OOB closure codes, of which I'm not a big fan. My only thought about using a hierarchical structure, as in the example you provided, is that it could become cumbersome for the IT staff when closing Incidents. From my experience, if the process isn't straightforward there is a tendency to just chose whatever so they can move forward. Having inaccurate data would defeat the purpose.
In my environment we don't really have a need to report down to this level. It would be interesting to hear your goals for using these closure codes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2014 02:36 PM
So we have a cause and sub-cause for our resolved issues. The cause is broad,
Change induced, capacity related, knowledge/training related, security related, or component issue. Each cause has different sub-causes, for example, change induced has the sub-causes of user originated, IT originated, or vender originated. Capacity related has sub-causes of Server performance, network, application/licensing, etc. If you are interested I can send you the full list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2014 09:17 AM
Thanks Matt. I would really appreciate if you send me the list for my reference. This is really going to help us as till now we're only using few closure codes but it is not helping our teams and managers to do more analysis and trending based on these closure code. Thanks again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2014 03:43 PM
We are using a very basic set a closure codes for incidents:
- Solved
- Gone / Withdrawn
- Passed to Change Management
- Unable to solve
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/