The Change Request Details screen displays and manages a single IT change request identified by itsDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
id parameter and is accessible at /it/changes/:id.
Overview
The page header shows the change-request title and CR number, with context-sensitive action buttons that vary by status. Fordraft requests: Edit, Submit for Approval, and Delete. For approved: Schedule and Start Implementation. For scheduled: Start Implementation. For implementing: Mark Complete and Rollback. The main layout is a two-column grid: the left column shows Details (status, risk, change type, description, and scheduled window), Implementation Plan, Rollback Plan, and Test Plan cards, plus an ImplementationChecklist when tasks exist. The right column shows a Risk Assessment card with impact/likelihood/complexity scores out of 5, an ApprovalWorkflowCard, a LinkedTicketCard, and a Timeline card.
Who it’s for
RequiresIT_PERMISSIONS.VIEW (outer ITViewGuard). No additional per-route permission gate.
Before you start
- You must hold
IT_PERMISSIONS.VIEWto access this screen. - The change request must exist.
- Edit is only available when status is
draftorrejected.
Steps
Open a change request
Navigate to
/it/changes and click any row, or follow a link from Approval Inbox or CAB Review.Review details and plans
Read the description, implementation plan, rollback plan, and test plan cards.
Advance the status
Click the appropriate action button (Submit for Approval, Schedule, Start Implementation, Mark Complete, or Rollback) based on the current status.
Key concepts
- cr_number — Auto-assigned change-request identifier; shows “Pending” until assigned.
- impact_score / likelihood_score / rollback_complexity_score — Integer values 1–5 that feed into the overall
risk_level. - ImplementationChecklist — Task checklist rendered when
useCRTasksreturns one or more tasks. - LinkedTicketCard — Associates the change request with a related service ticket via
related_ticket_id.
Related
IT Service Management
IT Service Management overview.
Governance & parity
Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/it.tsx
- src/cores/it/pages/changes/ChangeRequestDetailPage.tsx