Connect Assets schemas with changes

Connecting Assets object schemas with change management in Jira Service Management enables you to associate relevant Assets objects (such as hardware, software, or other resources) with change requests, ensuring that all affected items are tracked and accounted for during changes.

This setup provides visibility into Assets in change-related views, for example:

• Risk insights: View potential change conflicts on specific Assets objects.

• Change calendar: Track which Assets objects will be impacted by upcoming changes.

Read more about connecting Assets schemas with incidents.

Set up an Assets field for change management

To be able to connect Assets objects with a change, you must first create a custom issue field and map it to an Assets schema, so you can search and select objects in that field.

Step 1: Create a custom field for Assets

Create a custom field

1. From your Advanced IT service project, go to Project settings > Change management.

2. Select the Assets tab.

3. In the instructions table, select Create custom field.

4. On the page, select Create custom field again, and choose Advanced.

5. Select Assets objects as the field type.

6. Enter a name for the field. We suggest names that describe the field's purpose, like "Affected objects". Read more about creating custom fields.

7. Once you’re done, select Create. Creating this fields takes several minutes, so please keep waiting.

8. You’ll be redirected to Associate field page. In this page, select the project and the screens in that project that you wish to associate your custom field related to change and incident management. Some commonly used screens are:

   1. Jira Service Management: Change Create Issue Screen

   2. Jira Service Management: Change View/Edit Screen

   3. Jira Service Management: Incident Create Issue Screen

   4. Jira Service Management: Incident View/Edit Screen

9. Select Update.

Map Assets schemas with a custom field

1. Once you set the screens for your field, go back to the Custom fields and find your newly created custom field.

2. Select your field and switch to the Contexts tab.

3. Select Create, edit, or delete contexts.

4. Scroll down and select Edit Assets object(s) field configuration. This is where you will map Assets schemas with your field.

5. Determine how this field will behave in your changes by setting up the Assets field. Make sure to add the field to your request types. Read more about setting up an Assets object custom field.

Now your field is ready to be used in your changes. However, you’ll still need to activate it for your request types to make it visible.

Step 2: Activate the custom field to change request types

Before you’re all set to use the field, you must activate the field in your request types to make it visible in your change management features.

1. Go back to your service project and navigate to Project settings > Change management.

2. Switch to the Assets tab.

3. Scroll down to the second step, and find the custom field you created under request types.

4. Select the checkbox to make sure your field is now appearing in relevant change management screens.

Once completed, the custom field will now be visible on the selected change request types, in relevant screens like the change detail, change calendar, and risk insights. Users will be able to search for and add Assets objects from mapped schemas directly within these requests, enhancing the visibility and traceability of Assets objects affected by each change.