Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Edit Change Request screen allows updating a change request that is in draft or rejected status and is accessible at /it/changes/:id/edit.

​
Overview

The page loads the existing change request via useChangeRequest. If the request is not in draft or rejected status, a message is shown that it cannot be edited, with a link back to the detail view. The form is organized into three tabs: Basic Info (title, description, change type: standard/normal/emergency, category: infrastructure/application/security/network/database/other), Risk Assessment (rendered by RiskAssessmentForm with impact, likelihood, and rollback complexity scores), and Planning (implementation plan, rollback plan, test plan text areas). On save, updateChangeRequest is called and the user is redirected to the change-request detail page.

​
Who it’s for

Requires IT_PERMISSIONS.VIEW (outer ITViewGuard). No additional per-route permission gate.

​
Before you start

  • You must hold IT_PERMISSIONS.VIEW to reach this route.
  • The change request must be in draft or rejected status; other statuses redirect to the read-only detail view.

​
Steps

1

Open the edit form

From the change-request detail page (when status is draft), click Edit.
2

Update basic info

On the Basic Info tab, update the title, description, change type, and category.
3

Adjust risk assessment

On the Risk Assessment tab, update the impact, likelihood, and rollback complexity scores.
4

Update planning documents

On the Planning tab, update the implementation plan, rollback plan, and test plan.
5

Save changes

Click Save Changes. On success, you are redirected to the change-request detail page.

​
Key concepts

  • change_type — Values: standard, normal, emergency.
  • category — Values: infrastructure, application, security, network, database, other.
  • RiskAssessmentForm — Shared component for entering impact, likelihood, and rollback complexity scores.

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.
  • src/routes/it.tsx
  • src/cores/it/pages/changes/EditChangeRequestPage.tsx