Bulk update Assets Object custom fields via External System Import

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

Summary

Currently, it's not possible to bulk update Asset Objects in a large number of Issues. However, this is achievable via External System Import with a CSV file.

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 issue that already has Objects added to anAsset 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 below example, 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: Issue Key, Summary, and the Custom Field column. 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 like:

A table showing Summary, Issue Key, and a Custom Field (User Device).  Issue keys IO-72, IO-73, IO-74, and IO-75 are listed with their corresponding custom field values. The custom field values are UUIDs that appear to increment except for IO-74.

Or, if you're a text file aficionado:

Issue 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 mapped to User Device, Issue key to Issue Key, and Summary to Summary.  Additional instructions explain how to handle multiple attachments, versions, components, or comments and the use of custom fields for sub-tasks. Next and Back buttons are available to navigate the import process.

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.


Last modified on Feb 6, 2025

Was this helpful?

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