C07 - Change Requests that Erred Out
This report provides details of those changes that were not successful during implementation along with relevant details to do a post-implementation review. This report also provides visibility into the tasks that failed for the unsuccessful change request.
Usage
Use this report to conduct a Post Implementation Review (PIR) of unsuccessful change requests, to understand the causes behind the failed implementation.
Report assumptions
- Change requests are considered "errored out" when they have a status of Closed and a Status Reason of Unsuccessful or Backed Out.
- Tasks are consider failed when the task status is Closed and the status reason is Failed.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*