Object types exceeding the limit of unique constraints

This insight checks whether any of your object types exceed the limit of attributes that require unique values. If they do, your migration will be blocked by a pre-migration check in the Jira Cloud Migration Assistant.

What are unique attributes?

In Assets, you can configure an attribute to require unique values. Once you do and provide a value for this attribute, the same value can't be used again for the related object type. This setting is often used for identifiers, such as serial numbers, to avoid duplicating objects.

Learn more about attributes set as unique

What’s the recommendation?

To unblock your migration, you need to review affected object types and reduce their number of unique attributes to a maximum of 2.

Reconfigure your attributes

Follow these steps to clean up attributes in the affected object types.

Download affected object types

When viewing this recommendation in Portfolio insights, you'll be able to download the affected object types in a CSV file. The file includes:

• URL of the object type, including its ID

• Count of unique attributes for each object type

Reconfigure your attributes

To reconfigure attributes:

1. Open each affected object type by selecting the URL. If you can't access the URL, you can also copy the ID and search for it in Assets.

2. Switch to the Attributes tab.

3. Review the attributes to find the unique ones. You'll need to open each attribute to check whether it's configured as unique. Start with attributes that look like identifiers, such as ID, Key, or Serial number. To open attribute settings, select Settings > Configure.

4. Reconfigure the attributes to no longer require unique values by unselecting the Unique setting in its configuration.

Learn more about attributes set as unique