Change request status reasons

Planning In Progress

• Accepted—The change request is in a planning in progress status because the request is accepted.
• Assigned—The change request is in a planning in progress status because the request is assigned.
• Built—The change request is in a planning in progress status because the request analysis is done and all the tasks are added to the request.

Implementation in Progress

• In Rollout—The change request is in an implementation in progress status because the request is rolled out and released to the user.
• In Development—The change request is in an implementation in progress status because the request is in development.
• In Test—The change request is in an implementation in progress status because the request is in the testing phase.
• In Build—The change request is in an implementation in progress status because the request is in a in build status.
• In Rollback—The change request is in an implementation in progress status because the request is in a rollback state.
• In Documentation—The change request is in an implementation in progress status because the request is getting documented.
• In Verification—The change request is in an implementation in progress status because the request is in a verification state.

Pending

• On Hold—The change request is pending because the request is on hold.
• Future Enhancement—The change request is pending because the request needs future enhancement.
• Manager Intervention—The change request is pending because the request needs manager intervention.
• Miscellaneous—The change request is pending because of any other reason than the statuses mentioned here.
• Support Group Communication—The change request is pending because of a pending support group communication.
• Task Review—The change request is pending because of a task review.
• Vendor Purchase— The change request is pending because of vendor purchase.

Rejected

• Insufficient Task Data—The change request is rejected because of insufficient data related to the task.
• Insufficient Change Data—The change request is rejected because of insufficient data related to the request.
• Schedule Conflicts—The change request is rejected because of schedule related conflicts.

Completed

• Final Review Required—The change request is completed because a final review of the request is required.
• Final Review Complete—The change request is completed because a final review of the request is complete.
• Additional Coding Required—The change request is completed because additional coding is required.

Closed

• Successful—The change request is closed because the request is successful.
• Successful with Issues—The change request is closed because the request is successful, but with issues.
• Unsuccessful—The change request is closed because the request is unsuccessful.
• Backed Out—The change request is closed because the request is backed out.
• Automatically Cancelled—The change request is closed because the request is automatically cancelled.

Cancelled

• No Longer Required—The change request is cancelled because the request is no longer required,
• Resources Not Available—The change request is cancelled because resources are not available.
• To Be Re-Scheduled—The change request is cancelled because the request needs to be rescheduled.
• Funding Not Available—The change request is cancelled because funding is not available.

Pending

Work on the request has been suspended temporarily. The Status Reason field is required to describe the reason for interruption.

Relate CI

In the Plan & Schedule stage, you can search for configuration items and relate them to the change requests. For more information, see Working-with-related-configuration-items.

Rejected

The request has been rejected by an approver at any Approval Phase.

Cancelled

The request is no longer required or current change plans must be modified.