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: Bobbyebuh
New Today: 10
New Yesterday: 45
Overall: 230639

People Online:
Visitors: 99
Members: 0
Total: 99



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 Closure scenario
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Incident Closure scenario

Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion
View previous topic :: View next topic  
Author Message

Joined: Sep 04, 2014
Posts: 1

PostPosted: Wed Sep 10, 2014 4:13 pm    Post subject: Incident Closure scenario Reply with quote


I am new to this forum. I need answer to a situation given below.

Incident is created when a circuit is down. The IT Service Desk team keeps the incident open even when the issue is resolved for monitoring purposes. Should the team close the incident as soon as the circuit is restored and service is up and open a proactive problem ticket to monitor the circuit or should the team keep the incident open till the monitoring ( typically 3 to more days) is also satisfactory.
Back to top
View user's profile
Senior Itiler

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

PostPosted: Thu Sep 11, 2014 5:12 am    Post subject: Reply with quote


The first error is that if the service has been restored, the incident should be resolved and closed

Monitoring the circuit is something of work activity for the team that does the network monitoring

As for a proactive PM ticket, what exactly is going to be done - proactively ?

Is the circuit the correct b/w, the network and Telco equipment up to date s/w wise......
John Hardesty
ITSM Manager's Certificate (Red Badge)

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

Joined: Oct 07, 2014
Posts: 5

PostPosted: Wed Oct 08, 2014 5:23 am    Post subject: Problem logs need Reply with quote

I think you should document, and find out the root cause and add it on your Problems DB and to have pro-action to prevent the same issue can happen again. Incident must be closed after resolved.
Back to top
View user's profile

Joined: Dec 16, 2014
Posts: 10

PostPosted: Wed Dec 17, 2014 1:07 pm    Post subject: An incident is resolved when an incident is resolved. Reply with quote

If the incident has been resolved, then it is resolved and the ticket should reflect that state.

Depending on your processes (incident and problem) you are likely to either:

a) have determined that the root cause has not been identified and raised a problem ticket (or notified of a potential problem),

b) have recognized this as a repeat incident and raised a problem ticket (or notified of a potential problem),

c) done nothing / hoped that problem will pick up that this is a repeat / hope problem will pick up that the incident was resolved without a permanent fix / not do anything

Ultimately, you want to prevent this from happening again. If you leave the incident open and it reoccurs then that takes away any power that 'Problem' has for building a case to investigate the root cause (e.g. it may have happened 15 times but you only have 1 ticket and 1 low priority ticket doesn't add much weight to a case for investigating a problem).

The best approach for you is to ensure that your incident process smoothly flows into problem. This can be done in a number of ways, but our approach is to put accountability onto the team leaders of the teams who manage incidents to decrease incident numbers.... this ultimately drives some effort in problem management from the people who are most aware of repeat incidents.
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion 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.