JIRA (v15-10-2015)

jira_issues & Nested Structures

This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.

These items are marked with a *

Accounting for Deleted Issues

When an issue is hard-deleted in JIRA, the record for the issue will remain in your data warehouse. This happens because of the Replication Method the jira_issues table uses and how JIRA’s API functions.

• The jira_issues table is incrementally replicated based on the updated_at column. This means that rows with values in this column that are greater than or equal to the last recorded MAX value will be selected for replication. If a record is hard-deleted, there won’t be a value to check and thus no way to detect changes to the record.
• JIRA’s API doesn’t include a flag to indicate deletes.

The suggested workaround (although it may be a bit cumbersome) is to use the fields__status__name column - which indicates the current status of an issue - to track deletes. Before deleting the issue, you could change the status to something that would only indicate a delete and then use that status as a filter in your queries.

jira_issues Attributes

While we try to include everything JIRA has here, this may not be a full list of attributes. Refer to JIRA's documentation for a full list and description of each attribute.

• Issue ID (id)

• self

• key

• expand

• changelog

• description

• attachment*

• subtasks*

• labels*

• fixversions*

• comments*

• Creator Info

• Status Info

• Summary

• Votes

• Reporter

• Priority

• Issue Type

jira_projects & Nested Structures

This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.

These items are marked with a *

jira_projects Attributes

While we try to include everything JIRA has here, this may not be a full list of attributes. Refer to JIRA's documentation for a full list and description of each attribute.

• Project ID (id)

• avatarurls

• description

• expand

• key

• lead__active

• lead__avatarurls

• lead__displayname

• lead__key

• lead__name

• lead__self

• name

• projecttypekey

• projectkeys*

• self

jira_project_categories Attributes

While we try to include everything JIRA has here, this may not be a full list of attributes. Refer to JIRA's documentation for a full list and description of each attribute.

• Project Category ID (id)

• self

• name

• description

jira_project_roles & Nested Structures

This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.

These items are marked with a *

jira_project_roles Attributes

While we try to include everything JIRA has here, this may not be a full list of attributes. Refer to JIRA's documentation for a full list and description of each attribute.

• Project Role ID (id)

• self

• name

• description

• roles__actors*

jira_project_types Attributes

While we try to include everything JIRA has here, this may not be a full list of attributes. Refer to JIRA's documentation for a full list and description of each attribute.

• Project Type Key (key)

• formattedkey

• description18nkey

• icon

• color

jira_resolutions Attributes

While we try to include everything JIRA has here, this may not be a full list of attributes. Refer to JIRA's documentation for a full list and description of each attribute.

• Resolution ID (id)

• self

• name

• description

jira_users Attributes

While we try to include everything JIRA has here, this may not be a full list of attributes. Refer to JIRA's documentation for a full list and description of each attribute.

• User Key (key)

• active

• avatarurls

• displayname

• emailaddress

• key

• locale

• name

• self

• timezone