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: FQLER
New Today: 57
New Yesterday: 92
Overall: 141970

People Online:
Visitors: 74
Members: 0
Total: 74

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 - Defining a Child ticket
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Defining a Child ticket

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


Joined: Aug 31, 2009
Posts: 2

PostPosted: Wed Sep 02, 2009 2:44 am    Post subject: Defining a Child ticket Reply with quote

Anyone have advice on defining a child ticket?

Do we consider it a Child ticket if....
- Same application, same symptom
- Same application, multiple symptoms
- Same root cause (not always known in the Incident Management process)
- the service restoration actions in the Parent will restore service to the child also

Or can more than one of these apply? Why do I ask? Let me run some scenarios we've encountered by you all -

- 3 applications on the same server, server outage impacts all apps: Any calls Service Desk receives on the 3 apps should be logged as Child tickets?
- We know that when one piece of the mainframe is down it will impact X, X, X and X. Should any calls Service Desk receives on those be logged as Child tickets?

Appreciate any feedback. Smile
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Wed Sep 02, 2009 11:47 pm    Post subject: Reply with quote

Stacey,

no real need to start a new thread for this. But no harm either.

Okay, a "child" is a database construct (at least metaphorically if not in reality) and so it ought to depend on how you set things up.

If I was wanting to use the phrase "child incident" I would probably reject all of the options you suggest, but you really have to use the term in a way that is useful to you.

My personal preference would be to say that a "child ticket" is raised whenever a second or subsequent call is received for an incident already notified and being managed. In this way you have a record of everyone to notify/confirm that the incident is resolved or indeed to consult in the investigation of the incident (a pattern or common factor might emerge for example).

Your list illustrates why the term (like far too many terms in our industry) is not safe to use in mixed company (i.e. with people from different organizations) without making the precise context and intention clear. that is why it was difficult to answer your original question.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Back to top
View user's profile Send e-mail
nisarg
Newbie
Newbie


Joined: Jan 25, 2009
Posts: 11

PostPosted: Sun Sep 06, 2009 7:31 pm    Post subject: Reply with quote

I would like to share my views w.r.t the example you provided

If there is a server outage which has impacted 3 diffrent applications , then any related calls regarding these 3 applications should be logged as a child to the Parent Incident.

By doing this
the exact impact and damage caused by the outage can be measured.

Its easy also easy to confirm and measure once the issue is resolved
Back to top
View user's profile
smehdi
Newbie
Newbie


Joined: Dec 09, 2009
Posts: 16

PostPosted: Sat Dec 12, 2009 4:39 am    Post subject: Reply with quote

Hi All,

Ideally the impact of an outage should not be measured with the no. of child Incidents attached to a parent Incident but with the impact on the business.

For e.g , At a given time if any application is down and lets say at that time only person is using the application then definately we are going to receive one call and that could not belinked to the impact on the business.

I child the Incidents and eventually calculate how many extra calls have received due to the outage to calculate the impact on the service desk but not on the business.
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 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.