A Change is a request to deliver new functionality or to make updates to existing functionality, within a Release or Project. A Change lists the technical aspects of a functional change to a System and includes impacts, timings, approvals, and Stakeholders.
Changes can have workflows that allows administrators to control the way Changes are processed.
This article provides an overview of steps to add and edit a Change record in Release & Verify. See Introduction to Change to filter and find Changes in the Change grid.
You must have the following user permissions to create/edit a Change record in Release & Verify:
Release > Change
To create a Change:
.| Fields | Description |
|---|---|
| Name | Mandatory; Enter the Change name. |
| Portfolio Association | Mandatory; Select a Portfolio Association for the Change record. |
| Description | Free text; Enter a description for the Change. |
| Fields | Description |
|---|---|
| Status | Mandatory; Select a Change Status from the drop-down. You can customize the Change Status using the Change Status Customization. |
| Theme | Mandatory; Select a Change theme. You can customize the Change Theme using the Change Theme Customization. |
| Type | Mandatory; Select a Change type. You can customize the Change Type using the Change Type Customization. |
| Delivery Risk | Mandatory; Select the Change Delivery Risk from the drop-down. You can customize the Change Delivery Risk using the Change Delivery Risk Customization. |
| Priority | Mandatory; Select the Change priority. You can customize the Priority using the Change Priority Customization. |
| Business Value Score | Select a business value score from the drop-down. |
| External ID | Records the External ID from which the record was created. Value can only be updated via the APIs. It is non-editable via the UI |
| Fields | Description |
|---|---|
| Raised by | By default, this field displays your user name. Select a different user from the drop-down, if needed. |
| Owner | The data in this field is managed by the ‘Stakeholder‘ tab. |
| Assigned to | Select a user or User Group as an assignee to this Change from the drop-down. Adding an assignee enables the users to receive the email notifications related to this Change without being a stakeholder. |
Linked Changes provide a record of the relationships between other Changes, as well as a shortcut. To link a Change:
.
to add the Linked Change.Remove a Linked Change by clicking X.
If you are adding a Change, you need to save the Change first by clicking
section is grayed out for a new Change. You must have Update Change user permissions (see Pre-requisites) to add or remove the Linked Changes.
Fill in the fields in this section. This section contains custom fields and tabs, which administrators have added using Change Custom Fields Customization. These fields will vary between each Release & Verify installation. Consult your administrator for the procedure for filling in these fields.
The permission to see a custom field tab is set in Change Custom Fields Customization.
You can attach, download an existing attachment and delete the URLs and Files to the Change in this section. For details, see Add Attachment.
After making the required entries on the Change tab, click
.

Manage Stakeholders associated with your Change in the Stakeholders tab. For more information, see Manage Change Stakeholders.

Add Systems on this tab to indicate the impacted Systems by your Change. For more information, see Manage Change Systems.

Delivery Release is a view-only tab and it shows the list of Releases that are linked to this Change. For Releases to display on this tab, ensure that you have added the correct Systems in the Systems tab which in turn are associated with the Releases.
Releases must have the following association:
For more details, see Manage Delivery Release.

The Linked Items tab shows the TECRs that have had this Change record added to the Change connected to TECR panel under the Linked Change tab in TECRs. For more details, see Manage Linked Items.

The Comments tab allows you to add a comment and answer other users’ comments.
.
.
on the confirmation prompt.
.
After making all the entries, click
.
Workflows allow administrators to control the way Changes are processed. Using the Change Status Customization, administrators can set:
For instance, a Change Type might have a workflow based on the Change Statuses: Draft > Active > Complete. All User Roles might have permission to change the Change Status from ‘Draft’ to ‘Active’ (using the Status drop-down menu) but only a ‘Manager’ User Role might have permission to change the Change Status from ‘Active’ to ‘Complete’. This workflow allows managers to check each Change before it is completed.
If the Enable Change Workflow checkbox is selected in Change Status Customization, users can click Expand Workflow
to view the Change’s workflow path.
Clicking Collapse Workflow
hides the workflow.

You can lock or unlock your Change records with the ‘Lock Change’ user permission. If a Change record is locked other users cannot edit or delete it.
This means:
To lock or unlock a Change record, click
. For more information, see Lock/Unlock Changes.

Locked records will be grayed out.
Click
to view the Audit History of the record. For more details, see Quick Tips.
To copy a Change’s URL to the clipboard, click
. For details, see Quick Tips.