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.
InformationshinweisVergewissern Sie sich, dass das verwendete Konto Lesezugriff auf die Tabellen hat, die Sie abrufen möchten.
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:
Navigate to User menu > Account settings > Security > Create and manage API tokens.
Click Create API token.
Enter a name for your new API token.
Click Create.
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.
Füllen Sie die erforderlichen Verbindungseigenschaften aus.
Geben Sie einen Namen für die Verbindung in Verbindungsname ein.
Wählen Sie Verbindungsmetadaten öffnen aus, um nach der Erstellung Metadaten für die Verbindung zu definieren.
Klicken Sie auf Erstellen.
Connection settings
Setting
Description
Data gateway
Wählen Sie ein Data Movement gateway aus, wenn dies für Ihren Anwendungsfall erforderlich ist.
Informationshinweis
Dieses Feld ist für das Qlik Talend Cloud Starter-Abonnement nicht verfügbar, da dieses Abonnement Data Movement gateway nicht unterstützt. Wenn Sie eine andere Abonnementstufe haben und Data Movement gateway nicht verwenden möchten, wählen Sie Keine.
Weitere Informationen zu den Vorteilen von Data Movement gateway und den Anwendungsfällen, in denen es erforderlich ist, finden Sie unter Qlik Data Gateway - Data Movement.
Start Date
Geben Sie das Datum im Format MM/DD/YYYY ein, ab dem die Daten von der Quelle zum Ziel repliziert werden müssen.
Base URL
The 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 Email
Enter your email or username.
Password or Token
Enter your password or your generated token. When your Jira instance is cloud-hosted, use an API token.
Groups
Optional. User groups to include in replication.
Schema
Informationshinweis
Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.
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:
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.
avatarUrls: OBJECT, which is also a nested data structure.
16x16: STRING
24x24: STRING
32x32: STRING
48x48: STRING
displayName: STRING
self: STRING
assigneeType
STRING
componentBean
OBJECT
This is a nested data structure:
assignee: OBJECT, which is also a nested data structure.
accountId: STRING
active: BOOLEAN
avatarUrls: OBJECT, which is also a nested data structure.
16x16: STRING
24x24: STRING
32x32: STRING
48x48: STRING
displayName: STRING
self: STRING
assigneeType: STRING
description: STRING
id: STRING
isAssigneeTypeValid: BOOLEAN
lead: OBJECT, which is also a nested data structure.
accountId: STRING
active: BOOLEAN
avatarUrls: OBJECT, which is also a nested data structure.
16x16: STRING
24x24: STRING
32x32: STRING
48x48: STRING
displayName: STRING
self: STRING
name: STRING
project: STRING
projectId: INTEGER
realAssignee: OBJECT, which is also a nested data structure.
accountId: STRING
active: BOOLEAN
avatarUrls: OBJECT, which is also a nested data structure.
16x16: STRING
24x24: STRING
32x32: STRING
48x48: STRING
displayName: STRING
self: STRING
realAssigneeType: STRING
self: STRING
description
STRING
id
STRING
isAssigneeTypeValid
BOOLEAN
issueCount
INTEGER
lead
OBJECT
This is a nested data structure:
accountId: STRING
active: BOOLEAN
avatarUrls: OBJECT, which is also a nested data structure.
16x16: STRING
24x24: STRING
32x32: STRING
48x48: STRING
displayName: STRING
self: STRING
name
STRING
project
STRING
projectId
INTEGER
realAssignee
OBJECT
This is a nested data structure:
accountId: STRING
active: BOOLEAN
avatarUrls: OBJECT, which is also a nested data structure.
16x16: STRING
24x24: STRING
32x32: STRING
48x48: STRING
displayName: STRING
self: STRING
realAssigneeType
STRING
self
STRING
group_users
The group_users table contains the list of all users in a group. Users are ordered by username. Due to privacy reasons, the Jira API does not return the username in the results.
statusCategory: OBJECT, which is also a nested data structure.
colorName: STRING
id: INTEGER
key: STRING
name: STRING
self: STRING
statusColor: STRING
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 projectsproject 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.
Create a status in JIRA that will be applied to issues you want to delete.
Before deleting the issue, apply the status.
Allow Qlik Talend Cloud to extract and load the updated data into your destination.
Delete the issue.
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.
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.
avatarUrls: OBJECT, which is also a nested data structure.
displayName: STRING
emailAddress: STRING
key: STRING
name: STRING
self: STRING
timeZone: STRING
comment
STRING
created
DATE-TIME
id
STRING
issueId
STRING
properties
ARRAY
This is a nested data structure:
key: STRING
self
STRING
started
DATE-TIME
timeSpent
STRING
timeSpentSeconds
INTEGER
updateAuthor
OBJECT
This is a nested data structure:
accountId: STRING
active: BOOLEAN
avatarUrls: OBJECT, which is also a nested data structure.
displayName: STRING
emailAddress: STRING
key: STRING
name: STRING
self: STRING
timeZone: STRING
updated
DATE-TIME
visibility
OBJECT
This is a nested data structure:
type: STRING
value: STRING
Hat diese Seite Ihnen geholfen?
Wenn Sie ein Problem mit dieser Seite oder ihrem Inhalt feststellen, sei es ein Tippfehler, ein ausgelassener Schritt oder ein technischer Fehler, informieren Sie uns bitte!
