Downloadable reports for viewing Assets limit breaches

[#1]

Hello Atlassian Community,

Last year, we announced several changes that would be implemented for Assets, including new limits on object types and attributes that are designed to ensure the future reliability and functionality of Assets.

These limits are:

• A maximum of 120 attributes per object type.

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

• For URL, Email, and Select attributes:

  • A maximum cardinality of 50 for attributes that allow multiple values.

  • A total character limit of 2700 across all values within an attribute.

• Duplicate values in Unique attributes are not allowed (see below for more on this).

For a comprehensive list of data storage limits in Assets, please refer to this article.

What happens if I’m breaching the limits?

If your site is exceeds these limits, no data or current functionality will be lost. However, we will be unable to move your site onto the new underlying implementation of Assets designed for greater performance, reliability and scale. This will mean we are unable to continue providing you new features and improvements for Assets.

We ask that you take action to align with the new limits before Friday 13th of June, 2025.

What do I need to do?

If you are breaching any of the limits above, you will receive an email with links to four downloadable reports designed to make it easy for you to find the locations in your Assets data that require adjustment. The four reports are:

• Object types with greater than 120 attributes.

• Object types with greater than two unique constraints on attributes, and the names of those attributes.

• Objects with URL, Email or Select attributes which breach a limit, and the particular limit being breached.

• Objects within object types that contain duplicate values on an attribute configured to be unique.

If there are no issues of a particular type, the linked report will simply be empty and no action is required by you.

Each report will include information to help you find the problematic attribute, object, object type, including:

• schema_id - the ID of the object schema

• schema_name - the name of the object schema

• schema_key - the key of the object schema

• object_type_id - the ID of the object type

• object_type_name - the name of the object type

• object_id - the ID of the object

• object_name - the name / label of the object

• attribute_name - the object attribute

What are duplicate values on unique constraints?

These are instances of multiple objects within a particular object type containing the same value for an attribute, even though that attribute is configured as being unique. This could have occurred due to:

• The attribute being marked as unique after duplicate values had already been introduced.

• A bug that we discovered which may be affecting some customers.

Both of these issues are being resolved in our new underlying implementation for Assets.

If you receive an email indicating that one or more limits are being breached in Assets, review the linked reports carefully, and take action by removing or modifying the object types and attributes that are causing the problem.

If you don’t receive an email, then no limits are being breached - carry on! Please reach out to the support team if you have any questions.

Best regards,

Justin King
Senior Product Manager, Jira Service Management

[Sonya Petkunas]

I just received an email today about taking action and the email indicated that we were recently emailed about this. We have until June 13, 2025 and this was the first email we received. So needless to say, we are kind of scrambling to figure out if and how we are effected. 

[Sue Lund]

This was also the first email I can find on the subject.
The email was regarding our sandbox environment.  I have not seen anything for our production environment yet.

[Hayley Skelton]

I have a similar experience to Sue - first email received only today, and only for our sandbox environment. Thankfully there's only a couple of assets affected as we've just begun using them, but I suspect this could be very messy for some! For those of us in the commonwealth one of the days is taken by a public holiday as well

[Justin King]

Hi Sonya, Sue and Hayley, 

What may have happened here is that between the time that we sent our first notification and the most recent one, you switched from not breaching any limits to breaching some. Hopefully if this is what has happened the changes you need to make are very minimal? 

I apologise for this coming as a surprise. 

[Sue Lund]

Thank you, Justin.  I was just concerned that we didn't receive anything for our production environment.  However, I wouldn't be surprised if there are not breaches there.
We only had a couple fixes in the sandbox and they were easy.

[Hayley Skelton]

Thanks @Justin King What's stranger is I forwarded the notice onto our Architect to action but when he downloaded the reports the breached items I originally saw were no longer there. It's great that the reports are as at when you download the report, but odd that the breach 'disappeared' when no changes had been made. We've decided to leave things as it's our Sandbox anyway - we can always take it down and bring it back up with the updated experience.

[Justin King]

Hi @Hayley Skelton

If you like, please reach out to me at jking@atlassian.com and pass me your site URL. I'll double check for you that no actions are required. 

[Felix Herzog]

We've received the reports and have issues on:

• Object types with greater than two unique constraints on attributes, and the names of those attributes.

What is the recommended Action here?

We've set up a major object type "assets" and sub object types like:
laptop, mini-pc and camera (and more)

on the major "assets" object type we already have defined unique attributes:

• serial number

that are inherited to all sub object types

For some object types - at least that have network connectivity - we have introduced 

• mac address (wifi)
• mac address (LAN)
• hostname
• ip address

hese antries also need to be unique. So for many objects we have 5 unique attributes and in our eyes we won't change this... hoiw can we solve it? Allow non-uniquiness?