Jira Service Management Support

Your data will be imported from a CSV file. This is useful if you're still using spreadsheets (not judging) or have CSV files for all of your assets. Learn more about importing

You need to be an Assets Manager for an object schema to create, configure, and enable imports.

Before you begin

Here are some requirements for your CSV file:

CSV headers

The CSV file needs to have headers, as they are used to create the data locators for the imports. An empty header value is not allowed.

Multiple values

To divide multiple values (for the Assets Attributes with multiple cardinality), use || (2 pipe characters).

Import fields

Once you've chosen your import type, you'll need to enter details about it. Here's the description of fields you should see in Assets.

General fields

Here are general fields, common for every import type:

Name	Description
Name	The name of the import.
Description	The description for your convenience.
Concatenator	You can specify a default concatenator. When joining multiple data locators into one Insight attribute, this will be the default concatenator. One example could be to join two columns like "First name" and "Last name" into one attribute. So "Mathias" (first name) and "Edblom" (last name) will be concatenated as "Mathias Edblom" if using \s as concatenator. Enter \s for space-concatenated. To include a concatenate character, place the value between double quotes (i.e "\s").
Empty Values	Defines what should happen when a Data Locator is empty. Should the import remove the attribute value or just ignores it and leave the current value as is.
Unknown Values	Defines what should happen if a Data Locator is unknown to Insight. This could happen with attribute types like "Status" and "Select". The value can be added as an option or just ignore the value.
Date Format	Format for date fields in import source to convert dates into Insight. If left empty, Insight will automatically try to find correct format. The format should be specified according to the Java SimpleDateFormat guidelines.
Date/Time Format	Format for date/time fields in import source to convert dates into Insight. If left empty, Insight will automatically try to find correct format. The format should be specified according to the Java SimpleDateFormat guidelines.

Module fields

These fields are specific to an import type (module).

Setting	Description
Import from	Choose a file or URL.
URL	Protocol, Hostname, and Port of where to find the external CSV file. Example: http(s)://example.com/file.csv or file:///opt/csv/example.csv
File	Choose a file to upload.
Username	Optional username for basic authentication.
Password	Optional password for basic authentication.
Delimiter	The delimiter used in the file. Enter \t for tab-delimited. To include a delimiter character, place the value between double quotes. To include a delimiter or a double quote character, place each value between double quotes.

Scheduling fields

Scheduling fields are responsible for keeping your data in sync:

Name

Description

Synchronizing Account

The Jira user to use when synchronize data into Assets.

For LDAP and database imports, the account used for synchronization must have Jira admin permissions.

Cron Expression

The interval for the automatic synchronization.

Automatically Synchronize

If the import should be scheduled for automatic synchronization.

Pre-defined structure and configuration

In the next step, after you've filled in the required fields, Assets will ask you whether you want to create a predefined structure (object type mappings) and configuration (attribute mappings). Details of this will differ depending on the import type.

Here's some details for the CSV import:

Each column from the CSV file will be created as an Assets attribute of type Default Text, and configuration will be mapped accordingly.
The object type created will always be the same.
Some object type mappings are disabled by default. Make sure to select the relevant ones.

If you want to have different attribute types created by the import of the data from the CSV file, create the predefined structure and then change the attribute types.

Import configuration created

You can now view your import configuration, but it's not ready yet. You still need to create or review the object type and attribute mapping, and make sure there are no problems with your import configuration.

When you're ready, go to 2. Create object type and attribute mapping.

Before you go

Object type mapping settings

In the next step, you'll create the object mapping settings. Here are some settings specific to the CSV import type.

Name	Description
Selector	The selector for the CSV import is not used. Use AQL to filter any data from the CSV file

Jira Service Management Support

Products

Jira Software