New types for Services in Assets for Jira Service Management cloud

[#1]

Hello Atlassian Community,

We have an update to share regarding the Services schema in Assets for Jira Service Management cloud.

At present, only one object type exists in the Services schema in Assets for Jira Service Management - that of “Service.”

After Oct 31, 2024 we will be modifying the name of this object type to “Software services” and introducing three new object types to this schema: Applications, Business services and Capabilities.

These types exist as labels to help categorise the nature of the service and has no technical impact on the service. This change will align the model of Services in Assets with that of Services that exist in Jira Service Management projects.

What do I need to know?

We believe this change will have little to no impact on most customers. However, if the Service object type from the Services schema is referenced in any Assets Query Language (AQL) across your sites, you will have to amend this query to reflect the new object type name of “Software Services.”

Features where customers most commonly reference object types are:

• Assets object custom field
• Automation rules
• Assets in Confluence cloud
• Assets JQL function

Additional features where AQL can be used can be found here.

What do I need to do?

In preparation for this change, and to manage the transition to the new object type name, you can modify AQL to incorporate both the old name (Service) and the new name (“Software Services”).

For example:

objectType = Service 

can become

objectType IN (Service, "Software Services", "Capabilities", "Business Services", "Applications") 

By making this change prior to Oct 31, 2024 you can prevent any AQL references breaking when this change is rolled out.

[Chrissy Clements]

Thanks for the update, Caroline.  It is great to see a closer alignment with Compass.

[Masayuki Abe]

@Caroline Bartle 

The “Service” object type is used for the “Affected services” field and is configured as one of the data sources for the change calendar and conflict check.

Does this affect the behavior?

[Caroline Bartle]

@Masayuki Abe There will be no change to the behaviour of the Affected Services field, nor the Change Calendar as a result of the change described in this update.

[Rick Westbrock]

I am surprised that the new name is "Software services" plural because the general guidance given in the Atlassian documentation is that object type names should be singular i.e. "Software service". Same for the three new object type names.

Will the Affected services field allow selecting a service from the new object types in addition to Software services?

[Caroline Bartle]

@Rick Westbrock The affected services field will allow you to select all services types.

[Rene Prochnow]

Hi @Caroline Bartle

Regarding your last response to Rick, does this mean I will be only able to select objects within one of the 4 service types? Or will I be able to select objects from other service types (schemas) which we have created ourselves in the Asset module?

Thanks