Assets custom fields don't load for migrated issues


Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Summary

Learn why after migrating or importing Assets custom fields in Jira issues, the field values are corrupted.

The Assets fields values show the error message "This field needs to be configured with an object schema” in the destination site. You also can't edit the fields.

Why is this happening?

JSM Assets doesn't support migrations yet.

Assets custom fields don't store object values directly. Instead, they keep a reference to Assets objects. During issue migration, these fields are exported with references specific to the origin site. The destination site can't recognize the references, leading to the error. We have a feature request ticket to track this limitation:

  • JSDCLOUD-12773 - After importing or migrating Assets custom fields values to another site Jira will show an error for all Assets custom fields on Issue view

How can I migrate Assets fields?

As Assets fields aren't supported in migrations, you'll need to work around this limitation.

Bulk update the Assets custom field to use objects from the destination site's schema. Make sure to update all asset custom fields that were added to the issue view. If even one field still uses the origin site workspace ID, all asset fields in the issue will be broken.

Update Jira Assets fields via CSV

You can also use CSV Export and CSV Import features to bulk update Custom Field Values. The custom field value in the file to import should be in the format <WorkspaceID>:<ObjectID>.

  1. The Workspace ID of your site's Assets can be found accessing the endpoint https://[your-domain].atlassian.net/rest/servicedeskapi/assets/workspace.
  2. The Object ID is the integer you can find in the object key. For example, if your key is ASSET-123, then '123' is your object's ID.
Last modified on Jan 15, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.