# JIRA (v2)
Information note **JIRA extraction is supported by Stitch**
This integration is powered by [Singer's](https://www.singer.io/) JIRA tap and certified by Stitch. [Check out and contribute to the repo on GitHub](https://github.com/singer-io/tap-jira).
For support, contact [Support](https://community.qlik.com/t5/Support/ct-p/qlikSupport).
## JIRA integration summary
Stitch’s JIRA integration replicates data from a JIRA Cloud instance using the [JIRA Cloud REST API v2](https://developer.atlassian.com/cloud/jira/platform/rest/v2/). Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/jira#schema) section for a list of objects available for replication.
## JIRA feature snapshot
A high-level look at Stitch's JIRA (v2) integration, including release status, useful links, and the features supported in Stitch.
| **STITCH** | | | |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on February 28, 2020 | **Supported by**
the Info icon
Indicates if the integration is supported by Stitch or the Singer community. | [Stitch](https://community.qlik.com/t5/Support/ct-p/qlikSupport) |
| **Stitch plan**
the Info icon
The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**
the Info icon
Indicates if the integration is available as a source in Stitch Connect. | the Success icon
This version of the integration is available via the API.
Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon
Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.
The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon
This feature is supported for this version of the integration.
Supported | **Column selection**
the Info icon
The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon
This feature is supported for this version of the integration.
Supported |
| **Select all**
the Info icon
Indicates if the integration supports selecting all available tables and columns. | the Success icon
Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon
This feature is supported for this version of the integration.
Supported |
## Connecting JIRA
### JIRA setup requirements
To set up JIRA in Stitch, you need:
* **Access to the issues, projects, worklogs, etc. that you want to replicate.** Stitch is only able to access the same objects that the user authenticating the integration has access to. If this user doesn’t have access to specific datasets or records, Stitch will be unable to replicate them from JIRA. Refer to [JIRA’s documentation](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html#Managingprojectpermissions-permission_schemes) for more info about permissions in JIRA.
* **Certain date formats are not supported by this integration**. Records with date formats from the following locales will be skipped during replication:
* 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
### Step 1: Verify self-managed configuration
Information note **Note**: This step is only required if your JIRA instance is self-managed (hosted). Otherwise, skip this step.
* [Step 1.1: Verify your protocol support](https://help.qlik.com/en-US/stitch/integrations/saas/jira#verify-protocol-support)
* [Step 1.2: Whitelist Stitch’s IP addresses](https://help.qlik.com/en-US/stitch/integrations/saas/jira#whitelist-stitch-ips)
#### Step 1.1: Verify your protocol support
To connect to a self-managed JIRA instance, your server must use `HTTPs` as the protocol. Stitch does not support `HTTP` for security reasons.
When you complete the JIRA setup in Stitch, you’ll be asked to enter your JIRA base URL. If Stitch determines that the protocol is not `HTTPs`, connection errors will arise.
Before proceeding, verify that your server uses `HTTPs` as the protocol.
#### Step 1.2: Whitelist Stitch's IP addresses
If your self-managed JIRA instance is behind a firewall, you’ll also need to whitelist Stitch’s IP addresses before proceeding. This ensures that Stitch will be allowed to access the instance. If you’re unsure how to do this, contact a member of your technical team for assistance.
The IP addresses you’ll whitelist depend on the [**Data pipeline region** your account is in](https://help.qlik.com/en-US/stitch/security/supported-data-pipeline-regions).
1. [Sign into your Stitch account](https://app.stitchdata.com/), if you haven’t already.
2. Click **User menu (your icon) > Edit User Settings** and locate the **Data pipeline region** section to verify your account’s region.
3. Locate the list of IP addresses for your region:
* [North America region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#north-america-ip-addresses)
* [Europe region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#europe-ip-addresses)
4. Whitelist the appropriate IP addresses for your Stitch data pipeline region.
### Step 2: Generate a JIRA API token
Information note **Note**: This step is only required if your JIRA instance is cloud-hosted. Otherwise, skip this step.
To authenticate with a cloud-hosted JIRA instance, Stitch requires a JIRA username and an API token. In this step, you’ll generate an API token in JIRA.
1. Sign into your JIRA account.
2. Click the **user menu (your icon)** in the bottom left corner of the page.
3. Click **Profile**.
4. Click **Manage your account**.
5. Click the **Security** tab.
6. In the **API token** section, click the **Create and manage API tokens** link.
7. On the page that displays, click the **Create API token** button.
8. In the window that displays, enter a **Label** for the API token. For example: `Stitch`
9. Click **Create**.
10. A new window containing the API token will display. **Copy the token before closing the window**, as JIRA will only display it once.
### Step 3: Add JIRA as a Stitch data source
1. [Sign into your Stitch account](https://app.stitchdata.com/).
2. On the Stitch Dashboard page, click the **Add Integration** button.
3. Click the **JIRA** icon.
4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch JIRA” would create a schema called `stitch_jira` in the destination. **Note**: Schema names cannot be changed after you save the integration.
5. In the **Base URL** field, enter the base URL for your JIRA site. For example: `stitchdata.atlassian.net` or `stitchdata.atlassian.com`
**Note**: If you’re connecting a self-managed instance, your server must use the `HTTPs` protocol or Stitch will be unable to successfully connect.
6. In the **Username** field, enter the email address of the JIRA user you want to use to authenticate the integration. **Note**: Stitch will replicate only the issues, projects, worklogs, etc. that this user has access to. If this user doesn’t have access to specific datasets or records, Stitch will be unable to replicate them from JIRA.
7. In the **Password or Token** field:
* **If connecting a self-managed JIRA instance**, enter the password associated with the user in the **Username** field.
* **If connecting a cloud-hosted JIRA instance**, paste the API token you generated in [Step 2](https://help.qlik.com/en-US/stitch/integrations/saas/jira#generate-jira-api-token).
### Step 4: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your JIRA integration. This means that data **equal to or newer than this date** will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond JIRA’s default setting of **1 year**. For a detailed look at historical replication jobs, check out the [Syncing Historical SaaS Data](https://help.qlik.com/en-US/stitch/replication/syncing-historical-saas-data-resetting-replication-keys) guide.
### Step 5: Create a replication schedule
Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.
In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
JIRA integrations support the following replication scheduling methods:
* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)
* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)
* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.
**Please note that certain date formats are not supported by this integration**. Records with date formats from the following locales will be skipped during replication:
* 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
### Step 6: Set objects to replicate
Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).
The last step is to select the tables and columns you want to replicate. [Learn about the available tables for this integration.](https://help.qlik.com/en-US/stitch/integrations/saas/jira#schema)
**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.
* Selection options
* Individual tables and columns
* All tables and columns
For JIRA integrations, you can select:
1. **Individual tables and columns**
2. **All tables and columns**
Click the tabs to view instructions for each selection method.
1. In the integration’s **Tables to Replicate tab**, locate a table you want to replicate.
2. To track a table, click the **checkbox** next to the table’s name. A blue checkmark means the table is set to replicate.
3. To track a column, click the **checkbox** next to the column’s name. A blue checkmark means the column is set to replicate.
4. Repeat this process for all the tables and columns you want to replicate.
5. When finished, click the **Finalize Your Selections** button at the bottom of the screen to save your selections.
Information note **Important**: Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections. Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.
1. Click into the integration from the Stitch Dashboard page.
2. Click the **Tables to Replicate** tab.
3. In the list of tables, click the box next to the **Table Names** column.
4. In the menu that displays, click **Track all Tables and Fields**:
The Track all Tables and Fields menu in the Tables to Replicate tabThe Track all Tables and Fields menu in the Tables to Replicate tab
5. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.
### Initial and historical replication jobs
After you finish setting up JIRA, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.**
Information note
**Initial replication jobs with Anchor Scheduling**
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.
#### Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.
## JIRA table reference
Information note
**Schemas and versioning**
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for **version 2** of this integration.
This is the latest version of the JIRA integration.
Information note
**Table and column names in your destination**
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (`CusTomERs` > `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` > `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info.
### changelogs
The `changelogs` table contains info about the changelogs associated with an issue.
**Note**: Due to a JIRA limitation in the endpoint Stitch uses to replicate changelogs, only the 100 most recent changelogs for any individual issue can be replicated. Refer to [JIRA’s documentation](https://confluence.atlassian.com/jirakb/jira-cloud-rest-api-limits-the-number-of-changelogs-returned-938840277.html) for more info.
#### Replication requirements
To replicate this data:
1. The [`issues`](https://help.qlik.com/en-US/stitch/integrations/saas/jira#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](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html) is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [changelogs schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/changelogs.json "Opens in new tab: changelogs schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-issue-issueIdOrKey-changelog-get "Opens in new tab: JIRA API method") |
changelogs table foreign keys
| Join changelogs with | on |
| --- | --- |
| [issue_comments](https://help.qlik.com/en-US/stitch/integrations/saas/jira#issue-comments) | ``` changelogs.issueId = issue_comments.issueId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand author
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
displayName
STRING
emailAddress
STRING
key
STRING
name
STRING
self
STRING
timeZone
STRING
|
| --- |
| **created**
DATE-TIME |
| **historyMetadata**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand historyMetadata
activityDescription
STRING
activityDescriptionKey
STRING
actor
OBJECT
avatarUrl
STRING
displayName
STRING
displayNameKey
STRING
id
STRING
type
STRING
url
STRING
cause
OBJECT
avatarUrl
STRING
displayName
STRING
displayNameKey
STRING
id
STRING
type
STRING
url
STRING
description
STRING
descriptionKey
STRING
emailDescription
STRING
emailDescriptionKey
STRING
extraData
OBJECT
generator
OBJECT
avatarUrl
STRING
displayName
STRING
displayNameKey
STRING
id
STRING
type
STRING
url
STRING
type
STRING
|
| **id**
STRING |
| **issueId**
STRING |
| **items**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand items
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:
1. The [`projects`](https://help.qlik.com/en-US/stitch/integrations/saas/jira#projects) table must also be set to replicate, and
2. The `Browse Projects` [project JIRA permission](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html) is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [components schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/components.json "Opens in new tab: components schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-project-components/#api-rest-api-2-project-projectidorkey-component-get "Opens in new tab: JIRA API method") |
components table foreign keys
| Join components with | on |
| --- | --- |
| [projects](https://help.qlik.com/en-US/stitch/integrations/saas/jira#projects) | ``` components.componentBean.projectId = projects.id ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand assignee
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
16x16
STRING
24x24
STRING
32x32
STRING
48x48
STRING
displayName
STRING
self
STRING
|
| --- |
| **assigneeType**
STRING |
| **componentBean**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand componentBean
assignee
OBJECT
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
16x16
STRING
24x24
STRING
32x32
STRING
48x48
STRING
displayName
STRING
self
STRING
assigneeType
STRING
description
STRING
id
STRING
isAssigneeTypeValid
BOOLEAN
lead
OBJECT
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
16x16
STRING
24x24
STRING
32x32
STRING
48x48
STRING
displayName
STRING
self
STRING
name
STRING
project
STRING
projectId
INTEGER
realAssignee
OBJECT
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
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. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand lead
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
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. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand realAssignee
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
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:
1. The [`issues`](https://help.qlik.com/en-US/stitch/integrations/saas/jira#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](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html) is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [issue_comments schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/issue_comments.json "Opens in new tab: issue_comments schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-issue-issueIdOrKey-comment-get "Opens in new tab: JIRA API method") |
issue\_comments table foreign keys
| Join issue\_comments with | on |
| --- | --- |
| [changelogs](https://help.qlik.com/en-US/stitch/integrations/saas/jira#changelogs) | ``` issue_comments.issueId = changelogs.issueId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand author
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
displayName
STRING
emailAddress
STRING
key
STRING
name
STRING
self
STRING
timeZone
STRING
|
| --- |
| **body**
STRING |
| **created**
DATE-TIME |
| **id**
STRING |
| **issueId**
STRING |
| **jsdPublic**
BOOLEAN |
| **properties**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand properties
key
STRING
|
| **renderedBody**
STRING |
| **self**
STRING |
| **updateAuthor**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand updateAuthor
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
displayName
STRING
emailAddress
STRING
key
STRING
name
STRING
self
STRING
timeZone
STRING
|
| **updated**
DATE-TIME |
| **visibility**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand visibility
type
STRING
value
STRING
|
### issue\_transitions
The `issue_transitions` table contains info about issue transitions.
#### Replication requirements
To replicate this data:
1. The [`issues`](https://help.qlik.com/en-US/stitch/integrations/saas/jira#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](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html) is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Loading Behavior [](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-behavior)[the Info icon](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-behavior)[](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-behavior)** | Append-Only |
| **Primary Key ** | id |
| **Useful links** | [issue_transitions schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/issue_transitions.json "Opens in new tab: issue_transitions schema on GitHub")
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **hasScreen**
BOOLEAN |
| **id**
STRING |
| **isConditional**
BOOLEAN |
| **isGlobal**
BOOLEAN |
| **isInitial**
BOOLEAN |
| **issueId**
STRING |
| **name**
STRING |
| **to**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand to
description
STRING
iconUrl
STRING
id
STRING
name
STRING
self
STRING
statusCategory
OBJECT
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`](https://help.qlik.com/en-US/stitch/integrations/saas/jira#changelogs), [`issue_comments`](https://help.qlik.com/en-US/stitch/integrations/saas/jira#issue_comments), and [`issue_transitions`](https://help.qlik.com/en-US/stitch/integrations/saas/jira#issue_transitions).
**Note**: To replicate this data, the `Browse projects` [project JIRA permission](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html) for the project that the issue is in is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
#### Identifying deleted issues
When an issue is hard-deleted in JIRA, the record for the issue will remain in your destination. This is due to the nature of Stitch [Replication Keys](https://help.qlik.com/en-US/stitch/replication/replication-keys) and the design of JIRA’s API:
* **Replication Keys**: This table uses the values in the `` column to identify new and updated data for replication. If a record is hard-deleted, there won’t be a value for Stitch to check and thus no way to identify the change, meaning the record will remain in the destination.
* **JIRA’s API**: Currently, JIRA’s API doesn’t include a way to identify deleted issues.
To identify deleted issues, [Atlassian’s suggested workaround](https://answers.atlassian.com/questions/75537/how-do-i-find-if-an-issue-has-been-deleted) 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 Stitch to extract and load the updated data into your destination.
4. Delete the issue.
5. After Stitch 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. For example, the following query would return any issues that had been marked with a the deleted status:
```
SELECT *
FROM stitch_jira.issues
WHERE fields__status__name = 'Deleted'
```
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [JIRA documentation](https://docs.atlassian.com/jira/REST/ondemand/#api/2/issue-getIssue "Opens in new tab: JIRA documentation")
[issues schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/issues.json "Opens in new tab: issues schema on GitHub")
[JIRA API method](https://docs.atlassian.com/jira/REST/cloud/#api/2/search-search "Opens in new tab: JIRA API method") |
issues table foreign keys
| Join issues with | on |
| --- | --- |
| [changelogs](https://help.qlik.com/en-US/stitch/integrations/saas/jira#changelogs) | ``` issues.id = changelogs.issueId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand editmeta
fields
OBJECT
|
| --- |
| **expand**
STRING |
| **fields**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand fields
attachment
ARRAY
created
DATE-TIME
lastViewed
DATE-TIME
updated
DATE-TIME
|
| **fieldsToInclude**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **id**
STRING |
| **key**
STRING |
| **names**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **properties**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand properties
properties
OBJECT
|
| **renderedFields**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **schema**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **self**
STRING |
| **versionedRepresentations**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
### project\_categories
The `project_categories` table contains info about project categories.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [project_categories schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/project_categories.json "Opens in new tab: project_categories schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-projectCategory-get "Opens in new tab: JIRA API method") |
project\_categories table foreign keys
| Join project\_categories with | on |
| --- | --- |
| [projects](https://help.qlik.com/en-US/stitch/integrations/saas/jira#projects) | ``` project_categories.id = projects.projectCategory.id ``` |
project\_categories table schema
| **description**
STRING |
| --- |
| **id**
STRING |
| **name**
STRING |
| **self**
STRING |
### project\_types
The `project_types` table contains info about project types.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | key |
| **Useful links** | [project_types schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/project_types.json "Opens in new tab: project_types schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-project-type-get "Opens in new tab: JIRA API method") |
project\_types table schema
| **color**
STRING |
| --- |
| **descriptionI18nKey**
STRING |
| **formattedKey**
STRING |
| **icon**
STRING |
| **key**
STRING |
### projects
The `projects` table contains info about projects in your JIRA account.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [projects schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/projects.json "Opens in new tab: projects schema on GitHub")
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **components**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand components
assignee
OBJECT
accountId
STRING
active
BOOLEAN
applicationRoles
OBJECT
avatarUrls
OBJECT
displayName
STRING
emailAddress
STRING
expand
STRING
groups
OBJECT
key
STRING
locale
STRING
name
STRING
self
STRING
timeZone
STRING
assigneeType
STRING
description
STRING
id
STRING
isAssigneeTypeValid
BOOLEAN
lead
OBJECT
accountId
STRING
active
BOOLEAN
applicationRoles
OBJECT
avatarUrls
OBJECT
displayName
STRING
emailAddress
STRING
expand
STRING
groups
OBJECT
key
STRING
locale
STRING
name
STRING
self
STRING
timeZone
STRING
leadUserName
STRING
name
STRING
project
STRING
projectId
INTEGER
realAssignee
OBJECT
accountId
STRING
active
BOOLEAN
applicationRoles
OBJECT
avatarUrls
OBJECT
displayName
STRING
emailAddress
STRING
expand
STRING
groups
OBJECT
key
STRING
locale
STRING
name
STRING
self
STRING
timeZone
STRING
realAssigneeType
STRING
self
STRING
|
| **description**
STRING |
| **email**
STRING |
| **expand**
STRING |
| **id**
STRING |
| **issueTypes**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand issueTypes
avatarId
INTEGER
description
STRING
iconUrl
STRING
id
STRING
name
STRING
self
STRING
subtask
BOOLEAN
|
| **key**
STRING |
| **lead**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand lead
accountId
STRING
active
BOOLEAN
applicationRoles
OBJECT
avatarUrls
OBJECT
displayName
STRING
emailAddress
STRING
expand
STRING
groups
OBJECT
key
STRING
locale
STRING
name
STRING
self
STRING
timeZone
STRING
|
| **name**
STRING |
| **projectCategory**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand projectCategory
description
STRING
id
STRING
name
STRING
self
STRING
|
| **projectKeys**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **projectTypeKey**
STRING |
| **roles**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **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](https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html) is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [resolutions schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/resolutions.json "Opens in new tab: resolutions schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-projectCategory-post "Opens in new tab: JIRA API method") |
resolutions table schema
| **description**
STRING |
| --- |
| **iconUrl**
STRING |
| **id**
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](https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html) is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [roles schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/roles.json "Opens in new tab: roles schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-role-get "Opens in new tab: JIRA API method") |
roles table schema
| **actors**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand actors
avatarUrl
STRING
displayName
STRING
id
INTEGER
name
STRING
type
STRING
|
| --- |
| **description**
STRING |
| **id**
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](https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html) is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | accountId |
| **Useful links** | [users schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/users.json "Opens in new tab: users schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-user-search-get "Opens in new tab: JIRA API method") |
users table foreign keys
| Join users with | on |
| --- | --- |
| [changelogs](https://help.qlik.com/en-US/stitch/integrations/saas/jira#changelogs) | ``` users.accountId = changelogs.author.accountId ``` |
| [components](https://help.qlik.com/en-US/stitch/integrations/saas/jira#components) | ``` users.accountId = components.assignee.accountId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **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:
1. The [`projects`](https://help.qlik.com/en-US/stitch/integrations/saas/jira#projects) table must also be set to replicate, and
2. The `Browse Projects` [project JIRA permission](https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html) is required. Refer to [JIRA’s API documentation](https://help.qlik.com/en-US/stitch/integrations/saas/jira) for more info.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [versions schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/versions.json "Opens in new tab: versions schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-project-projectIdOrKey-versions-get "Opens in new tab: JIRA API method") |
versions table foreign keys
| Join versions with | on |
| --- | --- |
| [components](https://help.qlik.com/en-US/stitch/integrations/saas/jira#components) | ``` versions.projectId = components.componentBean.projectId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand operations
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. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand remotelinks
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](https://help.qlik.com/en-US/stitch/integrations/saas/jira) (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 [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Replication Key ** | updated |
| **Useful links** | [worklogs schema on GitHub](https://github.com/singer-io/tap-jira/blob/master/tap_jira/schemas/worklogs.json "Opens in new tab: worklogs schema on GitHub")
[JIRA API method](https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-worklog-updated-get "Opens in new tab: JIRA API method") |
worklogs table foreign keys
| Join worklogs with | on |
| --- | --- |
| [changelogs](https://help.qlik.com/en-US/stitch/integrations/saas/jira#changelogs) | ``` worklogs.issueId = changelogs.issueId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand author
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
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. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand properties
key
STRING
|
| **self**
STRING |
| **started**
DATE-TIME |
| **timeSpent**
STRING |
| **timeSpentSeconds**
INTEGER |
| **updateAuthor**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand updateAuthor
accountId
STRING
active
BOOLEAN
avatarUrls
OBJECT
displayName
STRING
emailAddress
STRING
key
STRING
name
STRING
self
STRING
timeZone
STRING
|
| **updated**
DATE-TIME |
| **visibility**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.