Update Jira Cloud Assets Custom Fields via External Import

Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.

Summary

Learn how to efficiently update Asset Objects in multiple work items using External System Import with a CSV file in Jira Cloud.

Solution

What do I need to know before the import?

Prior to the import, you'll need to get the following information:

  1. Your JSM Assets Workspace id; and

  2. Your Object(s) id;

JSM Assets Workspace ID

You can find your JSM Assets Workspace ID through different methods, such as using our REST API or by exporting to .csv any work item that already has Objects added to an Asset object field. The workspace ID should look like this:

c31785fc-7034-4281-814c-47e16553bce7

Object ID

The object ID can be found at its key. In the example below, the ID is "2222."

Details view of an object (asset AS-2222). Name, TAG, User, and Software fields are displayed. Edit, Comment, More, Object Graph, and Back to Object Type buttons are available.

Preparing the CSV file

With the Workspace and Object IDs, you can build our CSV file. You'll need at least three columns: Work Item Key, Summary, and Custom Field. During this setup, the Summary column can be left empty.

The Objects we'd like to add to the field should use a "workspace_id:object_id" format.

Using a spreadsheet editor, here's an example of how it should look:

A table showing Summary, Work Item Key, and a Custom Field (User Device).  Work Item keys IO-72, IO-73, IO-74, and IO-75 are listed with their corresponding custom field values. The custom field values are UUIDs

Or, if you're a text file aficionado:

Work item key,Summary,Device IO-26,,c31785fc-7034-4281-814c-47e16553bce7:2222 IO-56,,c31785fc-7034-4281-814c-47e16553bce7:2468 IO-73,,c31785fc-7034-4281-814c-47e16553bce7:783 IO-2347,,c31785fc-7034-4281-814c-47e16553bce7:6420 IO-3456,,c31785fc-7034-4281-814c-47e16553bce7:9069 IO-45,,c31785fc-7034-4281-814c-47e16553bce7:2123 IO-236,,c31785fc-7034-4281-814c-47e16553bce7:9568 IO-72,,c31785fc-7034-4281-814c-47e16553bce7:1458 IO-3527,,c31785fc-7034-4281-814c-47e16553bce7:485

Onto the Import!

To import the data, follow the steps outlined in this article, making sure to map our three columns to the appropriate fields:

This screen displays the Fields mapping section of a Jira import process. A warning notes that using Issue Key mapping will update existing issues with matching keys from the CSV file. The user can map CSV fields to Jira fields. Currently, Device is

An empty Summary column will prevent unnecessary or unwanted updates to the Issues' Summary.

After the Import process is finished, you should see the proper Objects added to the mapped field.

Example Jira work item with a connected Asset object

Updated on May 8, 2025

Still need help?

The Atlassian Community is here for you.