Summary

Currently, due to JSDCLOUD-10914 and JRACLOUD-42307, it is not possible to perform bulk updates of 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".

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:

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:

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