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.

См. раздел Схема для получения списка объектов, доступных для репликации.

Preparing for authentication

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

Убедитесь, что используемая учетная запись имеет доступ для чтения к таблицам, которые требуется получить.

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:

Log into your Jira account.
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.

Creating the connection

Для получения дополнительной информации см. раздел Подключение к приложениям SaaS.

Заполните необходимые свойства подключения.
Заполните поле Имя подключения.
Установите флажок Открыть метаданные подключения, чтобы определить метаданные для подключения, когда оно будет создано.
Щелкните Создать.

Connection settings
Setting	Description
Data gateway	Выберите шлюз Шлюз движения данных, если этого требует текущий сценарий использования. Примечание к информации Это поле недоступно при использовании подписки Qlik Talend Cloud Starter, так как она не поддерживает Шлюз движения данных. Если используется другой уровень подписки или не требуется использовать Шлюз движения данных, выберите Нет. Для получения информации о преимуществах Шлюз движения данных и о сценариях, требующих его использования, см. раздел Шлюз данных Qlik — движение данных.
Start Date	Введите дату в формате `MM/DD/YYYY`, начиная с которой данные должны реплицироваться из источника в цель.
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

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:

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.
The Browse Projects project Jira permission is required.

Replication Method

CDC

Primary Key

Useful links

Jira API method

Join changelogs with	on
issue_comments	changelogs.issueId = issue_comments.issueId changelogs.author.accountId = issue_comments.author.accountId changelogs.author.accountId = issue_comments.updateAuthor.accountId
issue_transitions	changelogs.issueId = issue_transitions.issueId
issues	changelogs.issueId = issues.id changelogs.author.accountId = issues.fields.attachment.author.accountId
worklogs	changelogs.issueId = worklogs.issueId changelogs.author.accountId = worklogs.author.accountId changelogs.author.accountId = worklogs.updateAuthor.accountId
components	changelogs.author.accountId = components.assignee.accountId changelogs.author.accountId = components.componentBean.assignee.accountId changelogs.author.accountId = components.componentBean.lead.accountId changelogs.author.accountId = components.componentBean.realAssignee.accountId changelogs.author.accountId = components.lead.accountId changelogs.author.accountId = components.realAssignee.accountId
projects	changelogs.author.accountId = projects.components.assignee.accountId changelogs.author.accountId = projects.components.lead.accountId changelogs.author.accountId = projects.components.realAssignee.accountId changelogs.author.accountId = projects.lead.accountId
users	changelogs.author.accountId = users.accountId

author

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

created

DATE-TIME

historyMetadata

OBJECT

This is a nested data structure:

activityDescription: STRING
activityDescriptionKey: STRING
actor: OBJECT, which is also a nested data structure.
- avatarUrl: STRING
- displayName: STRING
- displayNameKey: STRING
- id: STRING
- type: STRING
- url: STRING
cause: OBJECT, which is also a nested data structure.
- avatarUrl: STRING
- displayName: STRING
- displayNameKey: STRING
- id: STRING
- type: STRING
- url: STRING
description: STRING
descriptionKey: STRING
emailDescription: STRING
emailDescriptionKey: STRING
extraData: OBJECT, which is also a nested data structure.
generator: OBJECT, which is also a nested data structure.
- avatarUrl: STRING
- displayName: STRING
- displayNameKey: STRING
- id: STRING
- type: STRING
- url: STRING
type: STRING

STRING

issueId

STRING

items

ARRAY

This is a nested data structure:

field: STRING
fieldId: STRING
fieldtype: STRING
from: STRING
fromString: STRING
to: STRING
toString: STRING

components

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

Replication requirements

Note: To replicate this data:

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

Replication Method

Full Table

Primary Key

Useful links

JIRA API method

Join components with	on
projects	components.componentBean.projectId = projects.id components.projectId = projects.id components.assignee.accountId = projects.components.assignee.accountId components.componentBean.assignee.accountId = projects.components.assignee.accountId components.componentBean.lead.accountId = projects.components.assignee.accountId components.componentBean.realAssignee.accountId = projects.components.assignee.accountId components.lead.accountId = projects.components.assignee.accountId components.realAssignee.accountId = projects.components.assignee.accountId components.assignee.accountId = projects.components.lead.accountId components.componentBean.assignee.accountId = projects.components.lead.accountId components.componentBean.lead.accountId = projects.components.lead.accountId components.componentBean.realAssignee.accountId = projects.components.lead.accountId components.lead.accountId = projects.components.lead.accountId components.realAssignee.accountId = projects.components.lead.accountId components.assignee.accountId = projects.components.realAssignee.accountId components.componentBean.assignee.accountId = projects.components.realAssignee.accountId components.componentBean.lead.accountId = projects.components.realAssignee.accountId components.componentBean.realAssignee.accountId = projects.components.realAssignee.accountId components.lead.accountId = projects.components.realAssignee.accountId components.realAssignee.accountId = projects.components.realAssignee.accountId components.assignee.accountId = projects.lead.accountId components.componentBean.assignee.accountId = projects.lead.accountId components.componentBean.lead.accountId = projects.lead.accountId components.componentBean.realAssignee.accountId = projects.lead.accountId components.lead.accountId = projects.lead.accountId components.realAssignee.accountId = projects.lead.accountId
versions	components.componentBean.projectId = versions.projectId components.projectId = versions.projectId
changelogs	components.assignee.accountId = changelogs.author.accountId components.componentBean.assignee.accountId = changelogs.author.accountId components.componentBean.lead.accountId = changelogs.author.accountId components.componentBean.realAssignee.accountId = changelogs.author.accountId components.lead.accountId = changelogs.author.accountId components.realAssignee.accountId = changelogs.author.accountId
issue_comments	components.assignee.accountId = issue_comments.author.accountId components.componentBean.assignee.accountId = issue_comments.author.accountId components.componentBean.lead.accountId = issue_comments.author.accountId components.componentBean.realAssignee.accountId = issue_comments.author.accountId components.lead.accountId = issue_comments.author.accountId components.realAssignee.accountId = issue_comments.author.accountId components.assignee.accountId = issue_comments.updateAuthor.accountId components.componentBean.assignee.accountId = issue_comments.updateAuthor.accountId components.componentBean.lead.accountId = issue_comments.updateAuthor.accountId components.componentBean.realAssignee.accountId = issue_comments.updateAuthor.accountId components.lead.accountId = issue_comments.updateAuthor.accountId components.realAssignee.accountId = issue_comments.updateAuthor.accountId
issues	components.assignee.accountId = issues.fields.attachment.author.accountId components.componentBean.assignee.accountId = issues.fields.attachment.author.accountId components.componentBean.lead.accountId = issues.fields.attachment.author.accountId components.componentBean.realAssignee.accountId = issues.fields.attachment.author.accountId components.lead.accountId = issues.fields.attachment.author.accountId components.realAssignee.accountId = issues.fields.attachment.author.accountId
users	components.assignee.accountId = users.accountId components.componentBean.assignee.accountId = users.accountId components.componentBean.lead.accountId = users.accountId components.componentBean.realAssignee.accountId = users.accountId components.lead.accountId = users.accountId components.realAssignee.accountId = users.accountId
worklogs	components.assignee.accountId = worklogs.author.accountId components.componentBean.assignee.accountId = worklogs.author.accountId components.componentBean.lead.accountId = worklogs.author.accountId components.componentBean.realAssignee.accountId = worklogs.author.accountId components.lead.accountId = worklogs.author.accountId components.realAssignee.accountId = worklogs.author.accountId components.assignee.accountId = worklogs.updateAuthor.accountId components.componentBean.assignee.accountId = worklogs.updateAuthor.accountId components.componentBean.lead.accountId = worklogs.updateAuthor.accountId components.componentBean.realAssignee.accountId = worklogs.updateAuthor.accountId components.lead.accountId = worklogs.updateAuthor.accountId components.realAssignee.accountId = worklogs.updateAuthor.accountId

assignee

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

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

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

issue_comments

The issue_comments table contains info about comments made on issues.

Replication requirements

To replicate this data:

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.
The Browse Projects project Jira permission is required.

Replication Method

CDC

Primary Key

Useful links

JIRA API method

Join issue_comments with	on
changelogs	issue_comments.issueId = changelogs.issueId issue_comments.author.accountId = changelogs.author.accountId issue_comments.updateAuthor.accountId = changelogs.author.accountId
issue_transitions	issue_comments.issueId = issue_transitions.issueId
issues	issue_comments.issueId = issues.id issue_comments.author.accountId = issues.fields.attachment.author.accountId issue_comments.updateAuthor.accountId = issues.fields.attachment.author.accountId
worklogs	issue_comments.issueId = worklogs.issueId issue_comments.author.accountId = worklogs.author.accountId issue_comments.updateAuthor.accountId = worklogs.author.accountId issue_comments.author.accountId = worklogs.updateAuthor.accountId issue_comments.updateAuthor.accountId = worklogs.updateAuthor.accountId
components	issue_comments.author.accountId = components.assignee.accountId issue_comments.updateAuthor.accountId = components.assignee.accountId issue_comments.author.accountId = components.componentBean.assignee.accountId issue_comments.updateAuthor.accountId = components.componentBean.assignee.accountId issue_comments.author.accountId = components.componentBean.lead.accountId issue_comments.updateAuthor.accountId = components.componentBean.lead.accountId issue_comments.author.accountId = components.componentBean.realAssignee.accountId issue_comments.updateAuthor.accountId = components.componentBean.realAssignee.accountId issue_comments.author.accountId = components.lead.accountId issue_comments.updateAuthor.accountId = components.lead.accountId issue_comments.author.accountId = components.realAssignee.accountId issue_comments.updateAuthor.accountId = components.realAssignee.accountId
projects	issue_comments.author.accountId = projects.components.assignee.accountId issue_comments.updateAuthor.accountId = projects.components.assignee.accountId issue_comments.author.accountId = projects.components.lead.accountId issue_comments.updateAuthor.accountId = projects.components.lead.accountId issue_comments.author.accountId = projects.components.realAssignee.accountId issue_comments.updateAuthor.accountId = projects.components.realAssignee.accountId issue_comments.author.accountId = projects.lead.accountId issue_comments.updateAuthor.accountId = projects.lead.accountId
users	issue_comments.author.accountId = users.accountId issue_comments.updateAuthor.accountId = users.accountId

author

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

body

STRING

created

DATE-TIME

STRING

issueId

STRING

jsdPublic

BOOLEAN

properties

ARRAY

This is a nested data structure:

key: STRING

renderedBody

STRING

self

STRING

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

issue_transitions

The issue_transitions table contains info about issue transitions.

Replication requirements

To replicate this data:

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.
The Browse Projects project Jira permission is required.

Replication Method	CDC
Loading Behavior	Append-Only
Primary Key	id
Useful links	JIRA API method

Join issue_transitions with	on
changelogs	issue_transitions.issueId = changelogs.issueId
issue_comments	issue_transitions.issueId = issue_comments.issueId
issues	issue_transitions.issueId = issues.id
worklogs	issue_transitions.issueId = worklogs.issueId

expand

STRING

fields

OBJECT

This is a nested data structure.

hasScreen

BOOLEAN

STRING

isConditional

BOOLEAN

isGlobal

BOOLEAN

isInitial

BOOLEAN

issueId

STRING

name

STRING

OBJECT

This is a nested data structure:

description: STRING
iconUrl: STRING
id: STRING
name: STRING
self: STRING
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 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:

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.

Replication Method

CDC

Primary Key

Useful links

JIRA documentation

JIRA API method

Join issues with	on
changelogs	issues.id = changelogs.issueId issues.fields.attachment.author.accountId = changelogs.author.accountId
issue_comments	issues.id = issue_comments.issueId issues.fields.attachment.author.accountId = issue_comments.author.accountId issues.fields.attachment.author.accountId = issue_comments.updateAuthor.accountId
issue_transitions	issues.id = issue_transitions.issueId
worklogs	issues.id = worklogs.issueId issues.fields.attachment.author.accountId = worklogs.author.accountId issues.fields.attachment.author.accountId = worklogs.updateAuthor.accountId
components	issues.fields.attachment.author.accountId = components.assignee.accountId issues.fields.attachment.author.accountId = components.componentBean.assignee.accountId issues.fields.attachment.author.accountId = components.componentBean.lead.accountId issues.fields.attachment.author.accountId = components.componentBean.realAssignee.accountId issues.fields.attachment.author.accountId = components.lead.accountId issues.fields.attachment.author.accountId = components.realAssignee.accountId
projects	issues.fields.attachment.author.accountId = projects.components.assignee.accountId issues.fields.attachment.author.accountId = projects.components.lead.accountId issues.fields.attachment.author.accountId = projects.components.realAssignee.accountId issues.fields.attachment.author.accountId = projects.lead.accountId
users	issues.fields.attachment.author.accountId = users.accountId

editmeta

OBJECT

This is a nested data structure:

fields: OBJECT, which is also a nested data structure.

expand

STRING

fields

OBJECT

This is a nested data structure:

attachment: ARRAY, which is also a nested data structure.
created: DATE-TIME
lastViewed: DATE-TIME
updated: DATE-TIME

fieldsToInclude

OBJECT

This is a nested data structure.

STRING

key

STRING

names

OBJECT

This is a nested data structure.

properties

OBJECT

This is a nested data structure:

properties: OBJECT, which is also a nested data structure.

renderedFields

OBJECT

This is a nested data structure.

schema

OBJECT

This is a nested data structure.

self

STRING

versionedRepresentations

OBJECT

This is a nested data structure.

project_categories

The project_categories table contains info about project categories.

Replication Method

Full Table

Primary Key

Useful links

JIRA API method

Join project_categories with	on
projects	project_categories.id = projects.projectCategory.id

description

STRING

name

STRING

self

STRING

project_types

The project_types table contains info about project types.

Replication Method

Full Table

Primary Key

key

Useful links

JIRA API method

color

STRING

descriptionI18nKey

STRING

formattedKey

STRING

icon

STRING

key

STRING

projects

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

Replication Method

Full Table

Primary Key

Useful links

JIRA documentation

Join projects with	on
project_categories	projects.projectCategory.id = project_categories.id
components	projects.id = components.componentBean.projectId projects.id = components.projectId projects.components.assignee.accountId = components.assignee.accountId projects.components.lead.accountId = components.assignee.accountId projects.components.realAssignee.accountId = components.assignee.accountId projects.lead.accountId = components.assignee.accountId projects.components.assignee.accountId = components.componentBean.assignee.accountId projects.components.lead.accountId = components.componentBean.assignee.accountId projects.components.realAssignee.accountId = components.componentBean.assignee.accountId projects.lead.accountId = components.componentBean.assignee.accountId projects.components.assignee.accountId = components.componentBean.lead.accountId projects.components.lead.accountId = components.componentBean.lead.accountId projects.components.realAssignee.accountId = components.componentBean.lead.accountId projects.lead.accountId = components.componentBean.lead.accountId projects.components.assignee.accountId = components.componentBean.realAssignee.accountId projects.components.lead.accountId = components.componentBean.realAssignee.accountId projects.components.realAssignee.accountId = components.componentBean.realAssignee.accountId projects.lead.accountId = components.componentBean.realAssignee.accountId projects.components.assignee.accountId = components.lead.accountId projects.components.lead.accountId = components.lead.accountId projects.components.realAssignee.accountId = components.lead.accountId projects.lead.accountId = components.lead.accountId projects.components.assignee.accountId = components.realAssignee.accountId projects.components.lead.accountId = components.realAssignee.accountId projects.components.realAssignee.accountId = components.realAssignee.accountId projects.lead.accountId = components.realAssignee.accountId
versions	projects.id = versions.projectId
changelogs	projects.components.assignee.accountId = changelogs.author.accountId projects.components.lead.accountId = changelogs.author.accountId projects.components.realAssignee.accountId = changelogs.author.accountId projects.lead.accountId = changelogs.author.accountId
issue_comments	projects.components.assignee.accountId = issue_comments.author.accountId projects.components.lead.accountId = issue_comments.author.accountId projects.components.realAssignee.accountId = issue_comments.author.accountId projects.lead.accountId = issue_comments.author.accountId projects.components.assignee.accountId = issue_comments.updateAuthor.accountId projects.components.lead.accountId = issue_comments.updateAuthor.accountId projects.components.realAssignee.accountId = issue_comments.updateAuthor.accountId projects.lead.accountId = issue_comments.updateAuthor.accountId
issues	projects.components.assignee.accountId = issues.fields.attachment.author.accountId projects.components.lead.accountId = issues.fields.attachment.author.accountId projects.components.realAssignee.accountId = issues.fields.attachment.author.accountId projects.lead.accountId = issues.fields.attachment.author.accountId
users	projects.components.assignee.accountId = users.accountId projects.components.lead.accountId = users.accountId projects.components.realAssignee.accountId = users.accountId projects.lead.accountId = users.accountId
worklogs	projects.components.assignee.accountId = worklogs.author.accountId projects.components.lead.accountId = worklogs.author.accountId projects.components.realAssignee.accountId = worklogs.author.accountId projects.lead.accountId = worklogs.author.accountId projects.components.assignee.accountId = worklogs.updateAuthor.accountId projects.components.lead.accountId = worklogs.updateAuthor.accountId projects.components.realAssignee.accountId = worklogs.updateAuthor.accountId projects.lead.accountId = worklogs.updateAuthor.accountId

assigneeType

STRING

avatarUrls

OBJECT

This is a nested data structure.

components

ARRAY

This is a nested data structure:

assignee: OBJECT, which is also a nested data structure.
- accountId: STRING
- active: BOOLEAN
- applicationRoles: OBJECT, which is also a nested data structure.
- avatarUrls: OBJECT, which is also a nested data structure.
- displayName: STRING
- emailAddress: STRING
- expand: STRING
- groups: OBJECT, which is also a nested data structure.
- key: STRING
- locale: STRING
- name: STRING
- self: STRING
- timeZone: STRING
assigneeType: STRING
description: STRING
id: STRING
isAssigneeTypeValid: BOOLEAN
lead: OBJECT, which is also a nested data structure.
- accountId: STRING
- active: BOOLEAN
- applicationRoles: OBJECT, which is also a nested data structure.
- avatarUrls: OBJECT, which is also a nested data structure.
- displayName: STRING
- emailAddress: STRING
- expand: STRING
- groups: OBJECT, which is also a nested data structure.
- key: STRING
- locale: STRING
- name: STRING
- self: STRING
- timeZone: STRING
leadUserName: STRING
name: STRING
project: STRING
projectId: INTEGER
realAssignee: OBJECT, which is also a nested data structure.
- accountId: STRING
- active: BOOLEAN
- applicationRoles: OBJECT, which is also a nested data structure.
- avatarUrls: OBJECT, which is also a nested data structure.
- displayName: STRING
- emailAddress: STRING
- expand: STRING
- groups: OBJECT, which is also a nested data structure.
- key: STRING
- locale: STRING
- name: STRING
- self: STRING
- timeZone: STRING
realAssigneeType: STRING
self: STRING

description

STRING

email

STRING

expand

STRING

issueTypes

ARRAY

This is a nested data structure:

avatarId: INTEGER
description: STRING
iconUrl: STRING
id: STRING
name: STRING
self: STRING
subtask: BOOLEAN

key

STRING

lead

OBJECT

This is a nested data structure:

accountId: STRING
active: BOOLEAN
applicationRoles: OBJECT, which is also a nested data structure.
avatarUrls: OBJECT, which is also a nested data structure.
displayName: STRING
emailAddress: STRING
expand: STRING
groups: OBJECT, which is also a nested data structure.
key: STRING
locale: STRING
name: STRING
self: STRING
timeZone: STRING

name

STRING

projectCategory

OBJECT

This is a nested data structure:

description: STRING
id: STRING
name: STRING
self: STRING

projectKeys

ARRAY

This is a nested data structure.

projectTypeKey

STRING

roles

OBJECT

This is a nested data structure.

self

STRING

simplified

BOOLEAN

url

STRING

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

Useful links

JIRA API method

description

STRING

iconUrl

STRING

name

STRING

self

STRING

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

Useful links

JIRA API method

actors

ARRAY

This is a nested data structure:

avatarUrl: STRING
displayName: STRING
id: INTEGER
name: STRING
type: STRING

description

STRING

INTEGER

name

STRING

self

STRING

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

Useful links

JIRA API method

Join users with	on
changelogs	users.accountId = changelogs.author.accountId
components	users.accountId = components.assignee.accountId users.accountId = components.componentBean.assignee.accountId users.accountId = components.componentBean.lead.accountId users.accountId = components.componentBean.realAssignee.accountId users.accountId = components.lead.accountId users.accountId = components.realAssignee.accountId
issue_comments	users.accountId = issue_comments.author.accountId users.accountId = issue_comments.updateAuthor.accountId
issues	users.accountId = issues.fields.attachment.author.accountId
projects	users.accountId = projects.components.assignee.accountId users.accountId = projects.components.lead.accountId users.accountId = projects.components.realAssignee.accountId users.accountId = projects.lead.accountId
worklogs	users.accountId = worklogs.author.accountId users.accountId = worklogs.updateAuthor.accountId

accountId

STRING

accountType

STRING

active

BOOLEAN

avatarUrls

OBJECT

This is a nested data structure.

displayName

STRING

emailAddress

STRING

expand

STRING

key

STRING

name

STRING

self

STRING

timeZone

STRING

versions

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

Replication requirements

Note: To replicate this data:

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

Replication Method

Full Table

Primary Key

Useful links

JIRA API method

Join versions with	on
components	versions.projectId = components.componentBean.projectId versions.projectId = components.projectId
projects	versions.projectId = projects.id

Join versions with

components

versions.projectId = components.componentBean.projectId

versions.projectId = components.projectId

projects

versions.projectId = projects.id

archived

BOOLEAN

description

STRING

expand

STRING

moveUnfixedIssuesTo

STRING

name

STRING

operations

ARRAY

This is a nested data structure:

href: STRING
iconClass: STRING
id: STRING
label: STRING
styleClass: STRING
title: STRING
weight: INTEGER

overdue

BOOLEAN

project

STRING

projectId

INTEGER

releaseDate

DATE-TIME

released

BOOLEAN

remotelinks

ARRAY

This is a nested data structure:

name: STRING
self: STRING

self

STRING

startDate

DATE-TIME

userReleaseDate

DATE-TIME

userStartDate

DATE-TIME

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

Useful links

JIRA API method

Join worklogs with	on
changelogs	worklogs.issueId = changelogs.issueId worklogs.author.accountId = changelogs.author.accountId worklogs.updateAuthor.accountId = changelogs.author.accountId
issue_comments	worklogs.issueId = issue_comments.issueId worklogs.author.accountId = issue_comments.author.accountId worklogs.updateAuthor.accountId = issue_comments.author.accountId worklogs.author.accountId = issue_comments.updateAuthor.accountId worklogs.updateAuthor.accountId = issue_comments.updateAuthor.accountId
issue_transitions	worklogs.issueId = issue_transitions.issueId
issues	worklogs.issueId = issues.id worklogs.author.accountId = issues.fields.attachment.author.accountId worklogs.updateAuthor.accountId = issues.fields.attachment.author.accountId
components	worklogs.author.accountId = components.assignee.accountId worklogs.updateAuthor.accountId = components.assignee.accountId worklogs.author.accountId = components.componentBean.assignee.accountId worklogs.updateAuthor.accountId = components.componentBean.assignee.accountId worklogs.author.accountId = components.componentBean.lead.accountId worklogs.updateAuthor.accountId = components.componentBean.lead.accountId worklogs.author.accountId = components.componentBean.realAssignee.accountId worklogs.updateAuthor.accountId = components.componentBean.realAssignee.accountId worklogs.author.accountId = components.lead.accountId worklogs.updateAuthor.accountId = components.lead.accountId worklogs.author.accountId = components.realAssignee.accountId worklogs.updateAuthor.accountId = components.realAssignee.accountId
projects	worklogs.author.accountId = projects.components.assignee.accountId worklogs.updateAuthor.accountId = projects.components.assignee.accountId worklogs.author.accountId = projects.components.lead.accountId worklogs.updateAuthor.accountId = projects.components.lead.accountId worklogs.author.accountId = projects.components.realAssignee.accountId worklogs.updateAuthor.accountId = projects.components.realAssignee.accountId worklogs.author.accountId = projects.lead.accountId worklogs.updateAuthor.accountId = projects.lead.accountId
users	worklogs.author.accountId = users.accountId worklogs.updateAuthor.accountId = users.accountId

author

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

comment

STRING

created

DATE-TIME

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

Помогла ли вам эта страница?

Если вы обнаружили какую-либо проблему на этой странице или с ее содержанием — будь то опечатка, пропущенный шаг или техническая ошибка, сообщите нам об этом!

Оставьте свой отзыв здесь