Copy Assets data
The feature described in this article is currently being rolled out to users participating our early access program. This feature will be available to everyone soon.
Assets is Jira Service Management’s native asset and configuration management tool for Premium and Enterprise plans. It allows you to track all kinds of assets and configuration items (CIs), enabling teams to easily link them to service requests, incidents, problems, changes, and workloads. Learn more about Assets
Licensing requirements for copying Assets
We won’t be able to copy Asset data if the destination site is using a Free or Standard license of Jira Service Management. To copy Asset data, the destination needs to upgrade to the Premium or Enterprise plans.
Assets data include objects defined within an object schema, which can represent various items such as laptops, servers, contracts, or vehicles. Additionally, Assets data also includes object types, each containing specific attributes that store detailed information.
When you choose to include Assets data while copying your Jira Service Management projects, it's important to note that some object schemas may be linked to projects that you haven't selected on the source site. You can still proceed to copy the object schemas, and we will ensure they are linked appropriately when the relevant projects are copied to the destination.
When Assets data is copied to the destination, both object keys and IDs will change in the background. This means:
Object QR codes will be modified
If your objects are integrated with third-party systems, we advise reviewing and adjusting the impacted objects in those external systems as necessary.
If your object IDs are referenced in AQL or AQL functions within JQL, some AQL queries might not update successfully during the data copy as we attempt to replace them with new IDs. We advise you to review the areas where these IDs are utilised in AQL to ensure they function as intended.
At this stage, copying Assets data does not support the following:
Services schema or service registry. We’re focusing on the core object schemas and data first, with more to come in future updates.
Data Manager. Support for Data Manager data copy will be available after Data Manager becomes generally available.
Assets reports
Validation scenarios and solutions
Before you can start copying, you need to run checks to identify potential problems or unwanted settings. We’ve described some of the Assets-related checks below:
Conflicting object schema keys
To copy Asset data, all object schemas must have unique keys between the source and destination. During validation, you’ll be able to download a CSV file that contains the object schemas with the same key. To resolve conflicts, you can delete duplicate schemas in your destination. Read more about deleting object schemas
Conflicting object schema names
To copy Assets data, all object schemas must have unique names between the source and destination. During validation, you’ll be able to download a CSV file that contains the object schemas with the same name. To resolve conflicts, you can change the names of the conflicting schemas in either your source or destination. Read more about changing object schema names
Usage limit for Assets reached on the destination
Your destination site has a usage limit for the number of objects it can store. By default, Premium and Enterprise plans allow 50,000 objects. If the data copy exceeds the usage limit set on your destination, we will inform you of the number of objects that exceed the allowable limit. To proceed with copying Assets data, you can delete some objects from either your source or destination or increase the asset usage limit. Read more about managing usage limit for Assets.
Object schema limit reached on the destination
Your destination site has a limit to store 100 object schemas. If the data copy exceeds the limit of 100 object schemas, we will inform you of the number of object schemas that exceed the limit. To proceed with copying Assets data, you can delete some object schemas from either your source or destination. Read more about deleting object schemas
Mismatched general configuration
We couldn’t copy the configuration of Assets from your source to the destination when they are configured differently. The configuration includes global reference types, statuses, and icons, all of which apply to all object schemas on the site. As a result, the copied object schemas will adopt the configuration of Assets from the destination.
To ensure that Assets function correctly on your destination site, we recommend reviewing and comparing the configurations between your source and destination. To access the general configuration of Assets:
From your service project:
Go to Assets and select General configuration.
Was this helpful?