Reminder - Changes coming into effect in Assets for Jira Service Management

[#1]

Hello Atlassian Community,

Last year, we announced a number of changes that would come into effect for Assets in Jira Service Management Cloud (most of them as of 30th of September 2024). We have delayed rolling out some of these changes, to allow more time for Assets customers to adjust if needed.

As of February and March 2025, these changes will now begin to take effect as we roll out improvements to the underlying Assets platform.

This is a reminder to all Assets customers to review these changes, and make any adjustments required to your Assets data and workflows. Doing so will allow us to roll out performance and reliability improvements to your sites as well other planned features and enhancements. In particular, if your Assets data exceeds any of the limits listed below, we will be unable to proceed.

New limits

• A maximum of 120 attributes per object type.

• A maximum of 2 unique constraints on attributes in an object type.

• For URL, Email and Select attributes:

  • A maximum cardinality of 50 for attributes with multiple values.

  • A total of no more than 2700 characters across all values within an attribute.

See this article for a complete list of limits in Assets for Jira Service Management, Cloud.

Changes to AQL

• It will no longer be possible to use order by on an attribute of a linked object using dot notation. For example order by Laptop.CPU will no longer be supported.

• Using dot notation(.) in the context of an import mapping will no longer be supported. Note this has no effect on use of dot notation(.) elsewhere.

• The connectedTickets() function will not be supported when nested within the inboundReferences() or outboundReferences().

• Project, Repository and Opsgenie Team attributes will no longer support partial match searches using the like, startsWith and endsWith operators

• TheendsWith operator will no longer be supported for users and groups attributes.

Changes to features

• Unique constraints will no longer be supported on attributes with a maximum cardinality more than 1.

• Unique constraints will no longer be supported on TextArea attributes.

• Data locators that reference specific array indexes (for example company.region[0].id) will no longer be supported in JSON import configurations.

Changes to the public REST API

• The summable attribute is longer a supported configuration option on the following endpoints:

  • /object (response)

  • /objectschema (response)

  • /objecttype (response)

  • /objecttypeattribute (request/response)

• The objectAttributeExists attribute from the ObjectTypeAttribute response payload will be removed across all endpoints.

• The removable attribute from the ReferenceType response payload will be removed across all endpoints.

We apologise for any disruption this may cause.

All the best,

Justin King
Senior Product Manager, Jira Service Management