Jira users import

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

By importing Jira users into Assets, you can manage user information more effectively within the Jira Service Management environment. This allows for better organization and accessibility of user data. More about importing

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

Skip to:

Importing Jira users

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. Imagine you have a group of 16 users called jira-servicedesk-user. You can use that group in Assets and retrieve it as Jira users objects. Depending on your mappings, you’ll see a configuration like this:

Example of Jira user import configuration

To create an Import structure:
  1. From your service project, go to Assets, then Object Schemas.

  2. From the Object Schemas list, select More actions and then select Configure.
    Configure an object schema window

  3. In the Schema configuration view, open the Import tab.

  4. Under the Import tab:

    • If there’s no import structure, you’ll see the message “You don't have any import connections yet”. Select Create Import configuration to create a new import structure.

    • If an import structure has already been created, select Create Configuration.
      Create import configuration window

  5. Select CSV import, then select Next.

  6. Fill in the General, Module, and Scheduling import fields.
    General fields of the import configuration

General fields

Here are general fields, common for every import type:

Name

Description

NameThe name of the import.
DescriptionThe 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.

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.

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.

Format for date/time fields in import source to convert dates into Insight. If left empty, Assets 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.

Specify if Assets should include inactive users from source.

Scheduling fields

Scheduling fields are responsible for keeping your data in sync:

NameDescription
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 ExpressionThe interval for the automatic synchronization.
Automatically SynchronizeIf the import should be scheduled for automatic synchronization.

7. Select Save Import Configuration.

Next, you can create a predefined structure and configuration for your import or create the object type and attribute mapping manually.

Predefined structure and configuration

In the next step, you can create the predefined structure and configuration manually or Assets can create them automatically. To make this process automatic, select:
  • Create predefined structure – this will create object types with attributes and relationships in the schema

  • Create predefined configuration – this will create type mappings in the import configuration.

Create predefined structure and configuration window

Import configuration created

If no predefined structure and configuration have been created, you still need to create the object type and attribute mapping. 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

SelectorThe selector for the Jira User import isn't used. User AQL to filter any data from the User data.

Known limitations

Currently, when importing Jira users into Assets, mapping and importing user properties directly within the Users import configuration isn’t possible.

Last modified on Dec 30, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.