Jira Service Management Support

This import type will import objects into Assets with a JSON file that holds the data to import. Learn more about importing

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

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 JSON file. Example: http(s)://example.com/rest/api/service or file:///opt/csv/example.json
File	Choose a file to upload.
Username	Optional username for basic authentication.
Password	Optional password for basic authentication.
Encoding	The encoding used in the file.

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.
Notifications	Select the check box to notify all object schema managers when an import fails.

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 Jira users import:

The predefined structure and configuration will be created based on the JSON file/URL present in the configuration.
Some object type mappings are disabled by default. Make sure to select the relevant ones.

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

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

Object type mapping settings

Name

Description

Selector

The selector for the JSON import.

Use [Attribute.*[Attribute]]

Exemple:

"items"
"items.item"
"json.data.systems"

Only JSON arrays are valid as selector.

Attribute mapping settings

Data locator:

Name	Description
attribute1[].attribite2[]..	The data locators provided are depending on the JSON and the selector configured.

Jira Service Management Support

Products

Jira Software