csv import with assett object custom field values

[Matej Štrba]

Dear Community,

I am reaching out to seek guidance on importing .csv files into Jira Service Management in Cloud. Our objective is to efficiently create multiple JIRA issues under a single Epic, with the issues being populated using the data provided in a .csv file.

The challenge arises with the custom fields designated as asset object types. The import process is unsuccessful when the data for these asset object type fields is presented in a format that is readily understandable by humans.

To better understand this, I conducted the process inversely by exporting issues that contain asset object custom field values into a .csv file. Upon examination, I noticed that the data for asset object custom fields appears in an unusual format:

Could someone explain to me the nature of this format?

Additionally, I am interested in learning if there is a viable method to import issues from a .csv file that includes asset object field values without encountering errors. And one more unpleasant piece of information: Custom fields are multi-select type :/

Appreciate your time and assistance on this matter.

Best regards,

Matej

[Hannes Obweger - JXL for Jira]

Hi @Matej Štrba,

welcome to the community!

If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields - including any Assets fields - much like you’d do in e.g. Excel or Google Sheets. It also allows bulk editing via copy/paste - within JXL, but also between JXL and pretty much any other tool, including Excel or Google Sheets. For assets, this copy/paste operation works based on the asset's name, as opposed to its (non-human-readable) ID. 

This is how this looks in action (Inventory is an assets field):

This is a copy/paste operation within a JXL sheet - but if you'd open a CSV file with asset names in e.g. Excel, copy your cells there, and paste them to JXL, that would work as well. 

(You can also use assets across JXL's many advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.)

Any questions just let me know,

Best,

Hannes