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


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: Shanna38
New Today: 3
New Yesterday: 26
Overall: 231714

People Online:
Visitors: 107
Members: 0
Total: 107



Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

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.


Select Interface Language:

Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Incident Ticket Closure
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Incident Ticket Closure

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

Joined: Feb 14, 2008
Posts: 77

PostPosted: Sat Feb 16, 2008 1:22 am    Post subject: Incident Ticket Closure Reply with quote

Hi Group,
one question regarding the Incident and Problem MGT process.
We have over here an INC process in place. Every opened ticket has 4 urgency levels behind it.
Question: when should the ticket be closed?
Scenario: User reports a defect in the application. The appropriate resolver group identifies that the defect can be solved by a code change and triggers off a RfC. The RfC runtime is approx. 2 days (incl. Testing, documentation etc.)
Should the INC ticket be closed after successful implementation of the RfC or after successful identification of the root cause?
Back to top
View user's profile
Senior Itiler

Joined: Sep 16, 2006
Posts: 3597
Location: London, UK

PostPosted: Sat Feb 16, 2008 1:31 am    Post subject: Reply with quote

This seems like an exam question rather than a work question.

The problem ticket should be closed when it is confirmed that the RFC successfull fixed the error by the resolver team (dev team ?)

The incident ticket should be closed after the implementation of the rfc and the successful confirmation that the inicident conditions no longer exist by the user who raised the incident
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Senior Itiler

Joined: Feb 14, 2008
Posts: 77

PostPosted: Sat Feb 16, 2008 1:35 am    Post subject: Reply with quote

Thats what I have thought as well. But I had this morning a discussion with one guy of the resolver group. According to them - waiting for a successful implementation would bring them into troubles with their SLA targets regarding ticket solution times.
Back to top
View user's profile
Senior Itiler

Joined: Aug 31, 2005
Posts: 550
Location: UK

PostPosted: Sat Feb 16, 2008 2:14 am    Post subject: Reply with quote

If there is no workaround to allow the user to achieve their requirements, then the incident is open until the RFC is implemented. You cannot tell the user that their incident is closed just to avoid breaching an SLA. The SLA IS breached, if it tales that long to overcome the issue. To pretend otherwise by fiddling the figures would not serve any purpose.
That said, it is possible to agree with your customer that the current state of the application does not include the facility in question, but the next release will. In that situation,the user will have to live with the lack of functionality until the Release happens. The Incident may then be closed (with the agreement of the user) with the explanation "User informed that this is not part of current functionality". This prevents tickets being open for 6 months, waiting for a release.

So - be pragmatic!
Liz Gallacher,
Accredited ITIL and ISO/IEC20000 Trainer and Consultant - Freelance
Back to top
View user's profile Send e-mail Visit poster's website
Senior Itiler

Joined: Feb 23, 2005
Posts: 458
Location: London

PostPosted: Sat Feb 16, 2008 2:18 am    Post subject: Reply with quote


I tend to agree with both of you and yes, it's likely that this will change the reporting for that team.

Incidents are about restoring service so if one requires a change to fix it then it has to stay open until the change is confirmed as successful. Tough luck! If they were able to put in place a suitable work around that still means that a problem ticket remains open until an rfc is successfully implemented.

Realistically then it might be that that team requires a different SLA metric looking at incident handling e.g. 'time to promote to Problem' etc. I hope that makes sense.


Back to top
View user's profile
Senior Itiler

Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Sun Feb 17, 2008 6:01 am    Post subject: Reply with quote

Agree with all

A Liz says " be pragmatic". It boils down to that in the end.

SLA's are there for a reason. Sometimes it is actually good if they breach once in a while - it tells you the reality of the situation. If they are fudged by closing tickets early - nothing will change. What people forget also is that SLA's can be re-negotiatied if required - an oftern under performed task.

So agree with all - incident stays open until a fix or workaround is put in place - even if this takes 2 days - what will happen is you will then have to investigate why they brached and you may find some intersting things. Why 2 days to put in a change for a number of incidents - can your emergency change process not get this through quicker - are you looking for too much admin , testing etc of an emergency change - do you even have an emergency change system?
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile
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

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.