Jira | Qlik Cloud Help
Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Jira

Jira is a cloud-based platform that allows bug tracking and agile project management.

Jira integration replicates data from a Jira Cloud instance using the Jira Cloud REST API v2.

See the Schema section for a list of objects available for replication.

Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

Information noteMake sure that the account you use has read access to the tables you want to fetch.

To set up a Jira connection in Qlik Talend Cloud, you need:

  • Jira permissions

    Qlik Talend Cloud can replicate only the Jira data that you can access (for example, issues, projects, and worklogs). If you cannot access specific records, Qlik Talend Cloud cannot replicate them. For more information, see Jira permission schemes.

  • Supported date locales

    Records that use date formats from the following locales are skipped:

    • Hungarian (Hungary): Magyar
    • Italian (Italy): Italiano
    • Japanese (Japan): 日本語 (日本)
    • Korean (South Korea): 한국어 (대한민국)
    • Polish (Poland): Polski
    • Thai (Thailand): ภาษาไทย
    • Turkish (Turkey): Türkçe
    • Chinese (China): 中文 (简体)
    • Chinese (Taiwan): 中文 (繁體)
    • Portuguese (Brazil): português (Brasil)
    • Portuguese (Portugal): Português (Portugal)
    • Vietnamese (Vietnam): Tiếng Việt

To generate your API token:

  1. Log into your Jira account.
  2. Navigate to User menu > Account settings > Security > Create and manage API tokens.
  3. Click Create API token.
  4. Enter a name for your new API token.
  5. Click Create.
  6. Copy and paste your API token into a secured file.

Before connecting to a self-managed (hosted) Jira instance, verify the following.

  • Your Jira server must use HTTPS. Qlik Talend Cloud does not support HTTP for security reasons. If the Jira base URL you enter in Qlik Talend Cloud does not use HTTPS, the connection will fail.
  • If your Jira instance is behind a firewall, allowlist Qlik Talend Cloud IP addresses so Qlik Talend Cloud can access the instance. For the current list, see Allowlisting domains and IP addresses.

Creating the connection

For more information, see Connecting to SaaS applications.

  1. Fill in the required connection properties.

  2. Provide a name for the connection in Connection name.

  3. Select Open connection metadata to define metadata for the connection when it has been created.

  4. Click Create.

Connection settings
SettingDescription
Data gateway

Select a Data Movement gateway if required by your use case.

Information note

This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.

For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.

Start Date

Enter the date, in the format MM/DD/YYYY, from which the data must be replicated from your source to your target.

Base URLThe base URL is the main address of your Jira instance. Enter the URL you use to open Jira in a browser, for example https://yourcompany.atlassian.net.
Username or EmailEnter your email or username.
Password or TokenEnter your password or your generated token. When your Jira instance is cloud-hosted, use an API token.
GroupsOptional. User groups to include in replication.

Schema

Information note

Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.

The schema and info displayed below is for version 2.

Depending on your destination, table and column names may not appear as they are outlined below.

changelogs

The changelogs table contains info about the changelogs associated with an issue.

Note: Due to a Jira limitation in the endpoint this connector uses to replicate changelogs, only the 100 most recent changelogs for any individual issue can be replicated. Refer to Jira documentation for more info.

Replication requirements

To replicate this data:

  1. The issues table must also be set to replicate. Note: When an issue is updated, all available changelogs for that issue will also be replicated.

  2. The Browse Projects project Jira permission is required.

Replication Method

CDC

Primary Key

id

Useful links

Jira API method

components

The components table contains info about components in projects in your JIRA account.

Replication requirements

Note: To replicate this data:

  1. The projects table must also be set to replicate, and
  2. The Browse Projects project Jira permission is required.

Replication Method

Full Table

Primary Key

id

Useful links

JIRA API method

issue_comments

The issue_comments table contains info about comments made on issues.

Replication requirements

To replicate this data:

  1. The issues table must also be set to replicate. Note: When an issue is updated, all the comments for that issue will also be replicated.
  2. The Browse Projects project Jira permission is required.

Replication Method

CDC

Primary Key

id

Useful links

JIRA API method

issue_transitions

The issue_transitions table contains info about issue transitions.

Replication requirements

To replicate this data:

  1. The issues table must also be set to replicate. Note: When an issue is updated, all the transitions for that issue will also be replicated.
  2. The Browse Projects project Jira permission is required.

Replication Method

CDC

Loading Behavior

Append-Only

Primary Key

id

Useful links

JIRA API method

issues

The issues table contains info about the issues in your JIRA instance. This table only contains core issue data - some data is located in other tables, such as changelogs, issue_comments, and issue_transitions.

Note: To replicate this data, the Browse projects project Jira permission for the project that the issue is in is required.

Identifying deleted issues

When an issue is hard-deleted in JIRA, the record for the issue will remain in your destination. Currently, Jira’s API doesn’t include a way to identify deleted issues.

To identify deleted issues, Atlassian’s suggested workaround is:

  1. Create a status in JIRA that will be applied to issues you want to delete.
  2. Before deleting the issue, apply the status.
  3. Allow Qlik Talend Cloud to extract and load the updated data into your destination.
  4. Delete the issue.

  5. After Qlik Talend Cloud finishes loading the data, use the fields__status__name field in your queries to filter issues with the deleted status you applied in step 2.

Replication Method

CDC

Primary Key

id

Useful links

JIRA documentation

JIRA API method

project_categories

The project_categories table contains info about project categories.

Replication Method

Full Table

Primary Key

id

Useful links

JIRA API method

project_types

The project_types table contains info about project types.

Replication Method

Full Table

Primary Key

key

Useful links

JIRA API method

projects

The projects table contains info about projects in your JIRA account.

Replication Method

Full Table

Primary Key

id

Useful links

JIRA documentation

resolutions

The resolutions table contains info about issue resolutions.

Note: To replicate this data, the Administer Jira global Jira permission is required.

Replication Method

Full Table

Primary Key

id

Useful links

JIRA API method

roles

The roles table contains info about the project roles in your JIRA account.

Note: To replicate this data, the Administer Jira global Jira permission is required.

Replication Method

Full Table

Primary Key

id

Useful links

JIRA API method

users

The users table contains info about the users in your JIRA account.

Note: To replicate this data, the Administer Jira global Jira permission is required.

Replication Method

Full Table

Primary Key

id

Useful links

JIRA API method

versions

The versions table contains info about versions in your JIRA account.

Replication requirements

Note: To replicate this data:

  1. The projects table must also be set to replicate, and
  2. The Browse Projects project Jira permission is required.

Replication Method

Full Table

Primary Key

id

Useful links

JIRA API method

worklogs

The worklogs table contains info about the worklogs in your JIRA account.

Note: For a worklog to be replicated, it must be set as Viewable by All Users, or the integration authenticating user (visible in the integration’s Integration Settings page), must be a member of the project role/group with permission to view the worklog.

If you’re missing worklogs, verify that you have the required permissions to access the worklog.

Replication Method

CDC

Primary Key

id

Useful links

JIRA API method

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here