Jira Service Management Support

You might want to collect more information about your Jira users or relate Jira users to customers. For this, you need to import your Jira users or specific user groups in Assets. 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
Restrict Groups	Only users in selected group(s) will be imported.
Include Inactive users	Specify if Assets should include inactive users from source.

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.

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 mapping settings. Here are some settings specific to the Jira users import type.

Object type mapping configuration

Name	Description
Selector	The selector for the Jira User import isn't used. User AQL to filter any data from the User data.

Jira Service Management Support

Products

Jira Software