Jira Service Management Support

Import structured data from an Assets object schema (Object Types, Attributes, and Objects). You can import data from another schema on the same server, or from an object schema on an entirely different server. Learn more about importing

Some use cases could be:

Synchronize two different servers, each running a different object schema.
Create a staging instance containing a subset of the full data from an object schema.
Synchronize data between a master server and a set of child servers that contain a subset of the full data.

This import type won't include your schema's automation rules, roles, or any other configuration.

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 Assets 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: Ignore - the existing value in the object will be retained and not overridden by an empty value. Remove - the existing value for the object will be removed, and replaced with an empty field value.
Unknown Values	Defines what should happen if a Data Locator is unknown. This could happen with attribute types like "Status" and "Select". Ignore - the value from CSV will be ignored and the object attribute will be left empty. Add - the value passed in the CSV file will be added to the list and the object attribute will be updated with the new 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
URL	The URL of the server that is running Jira with Assets.
Username	The username for authentication with the other server.
Password	The password for authentication with the other server.
Object Schema	The Name or Object Schema ID for the target server.

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.

Object collision

Because of the possibility the two synchronizing servers might contain objects with the same name, every object imported from another server is assigned an External Hash Key as an attribute. This hash key is built by appending the URL, schema ID, and the object key to create a longer, unique hash.

Pre-defined structure & 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 object schema import:

The predefined structure and configuration will be based upon the existing configuration of the target Assets object schema.
Some object type mappings are disabled by default, so 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 map any object references or attributes between your source and Assets.

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

Jira Service Management Support

Products

Jira Software