We currently have a Change Rule in place that requires a technician to add an impacted area to the change before they can submit it or modify it. Yesterday (6/10) our changes were fine and had the impacted areas associated with them. Early this morning we identified that some how our impacted areas were deleted on at least hundreds of change tickets (possibly more). I was able to do a query that found for changes created since June 1st, the following change tickets no longer have impacted areas associated with them: 54 Completed 32 Scheduled 29 Planning In Progress 16 Scheduled For Approval 11 Scheduled For Review 7 Draft 6 Cancelled 3 Implementation In Progress 2 Closed
However, not all changes lost their impacted area associated. I personally had a couple of changes assigned to me with impacted areas. One of them still has the impacted areas, while the other does not. I have reviewed our escalations and the escalations and nothing really jumps out. Has anyone else see this happen? ARS: 8.1.01 ITSM: 8.1.01 CMDB: 8.1.01 Midtier: Windows 2008 R2 ARS App: Sun Solaris Database: Oracle _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
