Change Templates

The Change Templates screen lists and manages reusable templates for IT change requests and is accessible at /it/changes/templates.

​

Overview

The Change Templates page loads all templates via useChangeTemplates and displays them in a data table with columns for name (linked to detail page), description, category, default risk level badge, auto-approve badge (Yes/No), and active/inactive status badge. A trash icon on each row opens a confirmation alert dialog before deleting the template. A New Template button links to /it/changes/templates/new to create a new template.

​

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 access this screen.

​

Steps

​

Key concepts

• default_risk_level — The risk level pre-populated when a change request is created from this template.
• auto_approve — Boolean flag; SME should confirm enforcement behavior in the approval workflow.
• is_active — Controls whether the template appears as an option when creating change requests.

​

Viewing a change template

The Change Template Details page (/it/changes/templates/:id) loads ITChangeTemplateDetailPage and manages a single change management template. This route is separate from provisioning templates (which live at /it/jml/templates/:id). Permission required: IT_PERMISSIONS.VIEW (it.view) via the module-level ITViewGuard. No additional per-route gate.

1. From the Change Templates list at /it/changes/templates, click a template name or the edit icon.
2. Edit the template name, description, category, default risk level, auto-approve flag, and active status as needed.
3. Update the default implementation plan, rollback plan, and test plan.
4. Save changes to update the template in place.

​

Creating a change template

The New Change Template page (/it/changes/templates/new) provides a form for creating reusable IT change request templates. Templates pre-populate the category, implementation plan, rollback plan, test plan, and default risk level when used in the New Change Request form. The page uses useChangeTemplateMutations for creation. The form collects: name (required), description, category, default_risk_level (low, medium, high), auto_approve (boolean toggle), is_active (boolean toggle, default true), default_implementation_plan, default_rollback_plan, and default_test_plan. On success, navigates to /it/changes/templates. Categories (code-defined): infrastructure, application, security, network, database, other. No explicit secondary permission gate at the route level beyond the outer ITViewGuard (it.view). Managing templates requires it.changes.manage. Before you start: hold the appropriate changes management permission (it.changes.manage) and define a standard implementation and rollback plan before creating the template.

1. Navigate to /it/changes/templates/new or click New Template from the Change Templates list.
2. Provide a descriptive name (e.g., “Standard Server Patch”) and select the appropriate category.
3. Choose the default risk level (low, medium, high) that will be pre-selected when this template is used.
4. Toggle Auto-Approve on if standard changes using this template should bypass manual approval.
5. Fill in the default Implementation Plan, Rollback Plan, and Test Plan. These will pre-populate the corresponding fields in new change requests that use this template.
6. Click Create Template. On success you are redirected to /it/changes/templates.

​

Related

Documentation sources

• src/routes/it.tsx
• src/cores/it/pages/changes/ChangeTemplatesPage.tsx
• src/cores/it/pages/changes/NewChangeTemplatePage.tsx
• src/cores/it/hooks/useChangeTemplateMutations.ts
• src/cores/it/types/change-management.ts