🎉 Connect Assets objects with change management and incidents in Jira Service Management
We’re excited to announce you can now connect Assets objects with changes & incidents in Jira Service Management!
Available for Premium and Enterprise customers, relevant Assets objects (such as hardware, software, or other resources) can be associated with change & incident requests, ensuring that you have a holistic view of the changes and all affected items are tracked and accounted for during changes.
Take a look here:
How it works
You’ll need to have selected Advanced IT Service Management template for projects in order to see change management.
In order to connect Assets objects with a change, you use an existing custom asset field or create a new custom asset field and map it to an Assets schema so you can search and select objects in that field. Once you’ve enabled the advanced templates, you can navigating to the change management page within Jira Service Management, where you will see the Assets tab at the top.
If you need to create a custom asset field, only admins can take this action. Select “Create custom field” in step one and then select “Create custom field” in the top right corner on the next window.
Afterwards, you will need to select “Assets objects” as your field type and enter a name for the field. We suggest names that describe the field's purpose like "Affected objects.”
In order to be used, some further configuration will be required. Head to the “Custom fields” tab on the left hand side, select “Contexts and default value,” and then select “Edit Assets object/s field configuration.”
Here, you will need to select the object schema so that this field could store object types related to the object schema and also select the attributes that should be shown in the issue view.
Once completed, you will need to return to the change management page for step two so that you can add the custom field to the request types you want to use.
Select where you would like to add a custom field, search for the field you custom field you may have just created on the right-hand side, and then drag it to where you would like. Once you are done, click “Save changes.”
When you return to the change management page, you should now see it added to all request types in your project. To enable it, select the check box and the “Shown in Risk Insights and Calendar” flag will confirm that it will now be shown in all change management features. For fields that are unchecked here, they will still be available in the issue view but will not be considered for other change management features like risk insights and the change calendar.
Let’s look at an example after the connection has been made. An employee needs a new keyboard because some of the keys aren’t working and has submitted a request for a specific piece of hardware. In the ticket, it can now be seen that there are “Risk summary” and “Changes” tabs. When you select the “Changes” tab, it shows that there is a change request in place to get the currently broken keyboard repaired.
And when you click on the change request above, you can also see the request that was submitted by the employee regarding their broken keyboard and needing a new one is linked.
Thoughts & feedback
What do you think? If you’d like to learn more about connecting Assets schemas with changes, refer to our support documentation.
We’d also appreciate any thoughts you’re willing to share on this new functionality. Feel free to drop any questions or suggestions here, or submit it via our feedback portal.
Was this helpful?
Thanks!
Prithwish Basu
7 comments