Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: ERZA
New Today: 12
New Yesterday: 58
Overall: 146170

People Online:
Visitors: 65
Members: 0
Total: 65

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - Resolve and close an incident if it just reports a bug?
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Resolve and close an incident if it just reports a bug?

 
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message
dam
Senior Itiler


Joined: Sep 05, 2007
Posts: 57

PostPosted: Thu Sep 06, 2007 7:01 pm    Post subject: Resolve and close an incident if it just reports a bug? Reply with quote

Hello,
The question is the following:

Ive got an email from a customer that report of an issue using the application. (like market estimations after year 2030 are clearly false)
I open an incident ticket.
After a first analysis it appears evident that this is related to an application bug.
I open a problem ticket to deal with the bug. At the same time lets imagine that there is no workaround for this issue (it may happen): what to do with the incident ticket?

I keep it unresolved and open till the underlying problem is solved (the bug is fixed)?
I resolve the incident as wont fix and I keep it open till the underlying problem is solved (the bug is fixed)?
I close the incident and I take care only of the problem ticket?

Thanks for your attention
Back to top
View user's profile
dboylan
Senior Itiler


Joined: Jan 03, 2007
Posts: 189
Location: Redmond, WA

PostPosted: Thu Sep 06, 2007 9:50 pm    Post subject: Reply with quote

The incident record should be linked to the problem record and left open. Any additional reports of users encountering the issue should have new incident records opened and linked to the same problem record. This way, by using the count of incidents linked to problem records, Problem Management can prioritize which problems to address.

Once Problem/Change/Release have implemented and confirmed that the problem has been resolved, then all the linked incidents can be resolved.

If you want to prevent the open incidents from being used as a negative reflection against your metrics, include a status for incidents of "Awaiting Problem Resolution" and exclude that status from your reporting.
Back to top
View user's profile
dam
Senior Itiler


Joined: Sep 05, 2007
Posts: 57

PostPosted: Thu Sep 06, 2007 10:36 pm    Post subject: Reply with quote

Hi dboylan,
Thanks for your answer. I agree with you on keeping the incident records open to give numbers to prioritise problem resolutions. (btw one of the major interest of implementing an itil approach to service support in my company is to have a, outer, measurable point of view on priorities etc. )
So removing the third hypothesis from the list above, it remains:

I keep it unresolved and open till the underlying problem is solved (the bug is fixed)?
I resolve the incident as wont fix and I keep it open till the underlying problem is solved (the bug is fixed)?

Id naturally tend to resolve the incident (keeping it open) even if there is no workaround. So second option. I gave a look at the Service Support book V2 5.6.4 and this is not 100% clear to me.

Regards.
Back to top
View user's profile
Guerino1
Senior Itiler


Joined: Jan 01, 2006
Posts: 500
Location: New Jersey

PostPosted: Tue Sep 11, 2007 9:55 pm    Post subject: Reply with quote

Hello Dam,

As the only workaround is to keep working and acknowledge that the results are wrong, it usually makes sense to keep the Incident open and linked to the Problem record. You will want to update the Incident record with the details, so that you have a knowledge history of what is going on, so that others can leverage that information, in the future. Also, if you're doing your job of constantly re-evaluating your Incidents, this Incident's Severity and Priority will get higher as you get closer to the year 2030.

NOTE: Many people will take the easy way out and close Incidents that are open longer than a period of time (let's say two years), because they don't want to sift through all the Incidents to see what should or shouldn't be closed. If people in your company do this, such an Incident will be closed because people will assume if it hasn't been addressed in all this time, it's not that important. Wrong assumption...

Anyhow, I hope this helps.

My Best,

Frank Guerino, CEO
TraverseIT
On-Demand ITIL Platform
Back to top
View user's profile Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.