I would like to be able to nest Services (setup a Parent/Child relationship) within Jira Service Management similar to how Objects work within Jira Assets. Does anyone know how to make that work?
@tyler.atchley There is no way to do that. You can set up a service request that has a custom field to select child services under it or use a form that provides the ability to select child services. There is no way to create a request type that has child request types under it. You can vote for the feature here https://jira.atlassian.com/browse/JSDCLOUD-6103
Thanks @Brant Schroeder. What I'm struggling with is JSM seems to have broken out a subsection of Assets, locked it down, and is using that locked Object Schema in conjunction with the "Affected services" custom field, also locked, to build out a lot of the Change Management form and automations.
If I were to list every service using the method provided then it's just going to be a giant single list of 100+ items vs. how it's traditionally setup within Assets where I can create new Object Types for each of my Applications with the Objects (services) nested under them.
If I break off from what comes out of the box and create my own Object Schemas, Types and Objects and then my own custom fields then Risk Summary on the Change ticket no longer works.
I'm trying to figure out how to make everything play together while still getting the additional benefits from Assets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.