Jira Service Management Support

You might want to import data from an internal or third-party system like BMC Remedy or Service Now. This article guides you through importing data from another database. Learn more about importing

You need to be a Jira admin to create, configure, and enable database imports.

Supported databases

We're using a common framework (jdbc) to connect to the database, so we support many databases:

Database Type	Driver
Microsoft SQL Server	com.microsoft.sqlserver.jdbc.SQLServerDriver
Oracle	oracle.jdbc.OracleDriver
PostgreSQL	org.postgresql.Driver
MySQL	com.mysql.jdbc.Driver

Import fields

Once you've selected 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, 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
URL	The database connection URL. If you want to connect to the Jira database, you can look into the dbconfig.xml in Jira_HOME to find the correct configuration and URL.
Driver	The driver class to use to connect to the database. Place the JDBC driver (.jar) to the <Jira_INSTALL>/lib* folder Don't forget to restart Jira after adding the driver to lib folder.
Username	The username used to authenticate.
Password	The password used to authenticate. You can enter the password for your database.

If you want to query the Jira database, you can look into the dbconfig.xml found in Jira_HOME directory, to find out the correct configuration.

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

Predefined structure and configuration is not available for this import type.

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 mappings. Here are some settings specific to the database import type.

Object type mapping configuration

Name

Description

Selector

The selector for the Database import is a SQL query. How to build SQL queries depends on the database type.

How to build up the selector (the SQL statement) depends on how you have configured the database connection. Below you will see some examples that will hopefully guide you in the right direction when setting this up.

Database Type

Example

Microsoft SQL Server

select * from <database.name>.<schema-name>.Application

<schema-name> is "dbo" as default so an example could be:

select * from dbname.dbo.Application

Oracle

select * from <schema-name>.Application

If <schema-name> is "Jiraschema" the query will be:

select * from Jiraschema.Application

PostgreSQL

select * from "Application"

MySQL

select * from Application

If you want to query the Jira database, you can look into the dbconfig.xml found in Jira_HOME directory, to find out the correct configuration, such as schema name etc.

Jira Service Management Support

Products

Jira Software