Assets for Jira Service Management cloud will have a new limits on URL, Email and Select attributes

[#1]

Hello Atlassian Community,

After 30th of September 2024 we will be introducing new limits regarding URL, Email and Select attributes. The limits are:

• A maximum cardinality of 50 for attributes with multiple values, OR

• A total of no more than 2700 characters for all values within an attribute (single or multiple values)

Whichever is reached first.

For Select attributes these limits apply to both attribute values and options.

For example this would mean that if a URL, Email or Select attribute had 50 values, then each value can on average contain 54 characters.

This is part of our effort to offer a more scalable, performant and reliable experience as we make major enhancements to the underlying platform that powers Assets. We believe these new limits will be sufficient for the vast majority of use cases in which Assets is utilised.

For the few customers with existing data that breaches this limit, we are asking these customers to please adjust their data to align with the limits by 30th of September 2024. If you are one of these customers we’ll be reaching out to you to see if we can help in any way.

By making these changes we can ensure your site can begin to utilise our improved Assets platform when it is completed and reap the vastly improved the scalability, performance and reliability it will offer. We’ll be announcing more about this soon.

We believe this change will have little to no impact on most customers. As always please reach out to us if you have any concerns or feedback.

All the best,

Justin King
Senior Product Manager, Jira Service Management

[Tim Eddelbüttel]

we are asking these customers to please adjust their data

Just saying, that this is a worse suggestion. Specially on URLs e.g. when you import data from an external datasource you can't simply "shorten" the urls. The product should be able to handle it if it's a valid url. Reaching scalability and better performance by saying "your data is wrong" and the customer must remove of modify the data is the wrong way here.

[Justin King]

Thanks for the feedback @Tim Eddelbüttel

You raise an excellent point. I'm discussing this with our team to see if we can alter how we go about this. Stay tuned.