Posted: Fri Jan 31, 2014 8:51 am Post subject: Occurrences and Cases (Incidents)
We use a CRM product right now and are trying to start implementing ITIL practices, Although we are not even close, my boss think he knows everything there is to know about the subject and here is todays scenario.. Please tell me he is way out in left field, granted I'm new to the practice too.
We upgraded a application to a new version, the old and new clients are on the computers, its time to remove the old client. there are probably 25 computers that need to be touched.
My thought process is... My boss should open an case (incident) for the request, assign it to my team, we will open a single change request and note all the computers we need to uninstall the old client from, then do the work.
Here is what my boss says... Open 25 cases, make one case a parent and all the others children, then work on each one until they are all done.
I don't really see any of this as an "incident" so to speak. There's nothing that I would consider break/fix. I believe this all should have been completed as part of the Change that helped deploy this new software.
Depending on the ITSM software you use, the exact work being done on a change can sometimes be tough to track so I can understand why you may want to do something like what you're suggesting, but I think it will skew metrics.
If you absolutely have to go with opening a "case" or 25 cases plus the parent. The Change would technically be the parent or what you'd want to relate everything to (which you may or may not be able to do). Given that you probably shouldn't be using incidents for this in the first place, I'd recommend one incident with the list of 25 computers and referencing the Change in that incident.
If these were true incidents, I'd be on board with what your boss said.
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