Our documentation now lives on the Atlassian Support site at https://support.atlassian.com/analytics/resources/.
Schema for Jira family of products
The Jira family of products share many of the same tables. In other words, data for the available Jira products in the Atlassian Data Lake are aggregated into the same set of tables.
To filter for specific Jira product data, use the Project type column from the Jira project table in the “Filters” section of your visual mode queries or the WHERE
clause of your SQL mode queries.
Interested in a visual diagram of this schema? Use the Visualize feature to view how the tables are connected.
Tables for project data
There are several tables for Jira project data:
Jira project
Jira project category
Jira project component
Jira project version
Jira project
SQL name for the table: jira_project
Lists your Jira projects
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| The default issue assignee setting for the project |
| No | String | TBD | An identifier of a project category, links to a record in the |
| Yes | String |
| Project description |
| Yes | String |
| Unique key for this project |
| No | String | <accountId> | An identifier of a user who is defined as the project lead |
| Yes | String |
| Project name |
| No | String |
| Unique project identifier. This is the Primary Key for project data. |
| No | String |
| The project identifier within a Jira site. It can be used to associate this record with the project identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| No | String |
| Status of the project |
| Yes | String |
| Type of the project |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
|
|
| No | String |
| A URL pointing to the project |
| No | String |
| 36-character unique site identifier |
Jira project category
SQL name for the table: jira_project_category
Lists project categories
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String | TBD | Identifier of a project category. This is the Primary Key for category data. |
| No | String |
| The category identifier within a Jira site. It can be used to associate this record with the category identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| Yes | String |
| The project category description |
| Yes | String |
| The project category name |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| 36-character unique site identifier |
Jira project component
SQL name for the table: jira_project_component
Lists the components defined for each project
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
|
| String |
|
|
| No | String |
| Identifier of a project component. This is the Primary Key for component data. |
| No | String |
| The component identifier within a Jira site. It can be used to associate this record with the component identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| Yes | String |
| The current status of this project component |
| No | String | <accountId> | The user identifier of the component lead |
| Yes | String |
| The name of the project component |
| No | String |
| Unique project identifier. Links to a record in the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| Unique site identifier |
Jira project version
SQL name for the table: jira_project_version
Lists the versions defined for each project
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| Yes | String |
| Project version description |
| Yes | String |
| The name of the project version |
| No | String |
| Unique project identifier. Links to a record in the |
| No | Date |
| The version’s release date |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | Number |
| The sequence order of versions, matching their order of appearance in the user interface |
| No | Date |
| The version’s start date |
| Yes | String |
| The current status of this project version |
| No | String |
| Identifier of a project version. This is the Primary Key for version data. |
| No | String |
| The version identifier within a Jira site. It can be used to associate this record with the version identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| No | String |
| 36-character unique site identifier |
Tables for issue data
Jira field metadata
Jira field option
Jira issue
Jira issue affected version mapping
Jira issue component mapping
Jira issue field
Jira issue fix version mapping
Jira issue history
Jira issue priority
Jira issue resolution
Jira issue status
Jira issue status category
Jira issue type
Jira field metadata
SQL name for the table: jira_field_metadata
Contains metadata about Jira fields (including custom fields)
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| The identifier of a Jira field. This is the Primary Key for Jira field data. |
| No | String |
| The field identifier within a Jira site. It can be used to associate this record with the field identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| Yes | String |
| The key of a Jira field. The key can hold a different value to the ID when it is defined by plugins. |
| Yes | String |
| The name of the field |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| Yes | String |
| The data type stored in the field |
| No | String |
| 36-character unique site identifier |
Jira field option
SQL name for the table: jira_field_option
Lists the option values you’ve defined for custom Jira fields such as select lists, multi-select lists, and radio buttons
For example, the Impact
field in Jira Service Management provides a selection of options to choose from: Minor/Localized
, Moderate/Limited
, Significant/Large
, Extensive/Widespread
. Each of those values is represented by a reference identifier (for example, 10000
, 10001
,…). The jira_issue_field
table captures for each issue where this field is defined what the selected option is (for example, 10002
), and jira_field_option
provides a way to translate that reference identifier to the corresponding value.
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| The identifier of a Jira field that the field option pertains to. Links to a record in the |
| No | String |
| The field identifier within a Jira site. It can be used to associate this record with the field identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| No | String |
| A globally unique identifier of a Jira field option |
| No | String |
| The field option identifier within a Jira site. For custom fields that use field options, the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| Yes | String |
| The content of the field option |
| No | String |
| 36-character unique site identifier |
Jira issue
SQL name for the table: jira_issue
Lists your Jira issues
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String | <accountId> | Unique identifier of the assignee |
| No | Datetime |
| Issue creation time (UTC time zone) |
| No | String | <accountId> | The identifier of the user who created the issue |
| Yes | String |
| Description of the issue |
| Yes | Datetime |
| The issue due date (UTC time zone) |
| Yes | String |
| A short description of the environment in which the issue occurred |
| No | String |
| Unique identifier of this issue. This is the Primary Key for issue data. |
| No | Number |
| The issue’s number within the project |
| No | String |
| The issue identifier within a Jira site. It can be used to associate this record with the issue identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| No | String |
| The identifier of the issue type. Links to a record in the |
| Yes | Array | [ | Array of label names |
| No | Number |
| Original estimate (in seconds) that was set (requires time-tracking enabled) |
| No | String |
| Identifier of the current issue priority. Links to a record in the |
| No | String |
| The identifier of the project. Links to a record in the |
| No | String | <accountId> | Unique identifier of the issue reporter |
| No | Datetime |
| Issue resolution time (UTC time zone) |
| No | String |
| Identifier of the issue resolution. Links to a record in the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| Identifier of the current issue status. Links to a record in the |
| Yes | String |
| Summary for the issue |
| No | Number |
| Estimate time (in seconds) remaining from original estimate (requires time-tracking enabled) |
| No | Number |
| Amount of logged work (in seconds). Field is |
| No | Datetime |
| Last issue update time (UTC time zone) |
| No | String |
| 36-character unique site identifier |
Jira issue affected version mapping
SQL name for the table: jira_issue_affected_version_mapping
Holds associations between issues and project versions that are affected versions for an issue
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String | TBD | Unique identifier of an issue. Links to a record in the |
| No | TIMESTAMP |
| Last refresh time for this record (UTC time zone) |
| No | String | TBD | Unique identifier of a project version affected by the issue. Links to a record in the |
| No | String |
| 36-character unique site identifier |
Jira issue component mapping
SQL name for the table: jira_issue_component_mapping
Holds associations between issues and project components
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String | TBD | Unique identifier of a project component. Links to a record in the |
| No | String | TBD | Unique identifier of an issue. Links to a record in the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| 36-character unique site identifier |
Jira issue field
SQL name for the table: jira_issue_field
Lists the contents of Jira fields
Table uses the following columns:
Not all custom field types are currently supported, but we’ll add additional fields over time.
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| The identifier of a Jira field. Use it together with the |
| No | String |
| Unique identifier of this issue. Use it together with the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| Yes | String |
| The contents of the field for this issue. The type of data represented by this string will depend on the field. |
| No | String |
| 36-character unique site identifier |
Jira issue fix version mapping
SQL name for the table: jira_issue_fix_version_mapping
Holds associations between issues and project versions that are fix versions for an issue
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| Unique identifier of an issue. Links to a record in the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| Unique identifier of a project version which is the fix version of the issue. Links to a record in the |
| No | String |
| 36-character unique site identifier |
Jira issue history
SQL name for the table: jira_issue_history
Tracks changes in issue data over time, similar to the History tab in issue Activity. Sometimes, several updates are applied to the issue at the same time. These updates will share the same changelog_id
value. For each of these groups of changes, there will be a row for each field that was updated.
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| The identifier of the user who applied the changes |
| No | String |
| An identifier for a group of issue updates |
| No | Datetime |
| The time of the issue changes (UTC time zone) |
| Yes | String |
| The name of the field that was updated |
| No | String |
| The identifier of the field that was updated |
|
| String |
| Indicates whether it is a default Jira field or a custom field |
| Yes | String |
| The value of the field before the change |
| Yes | String |
| A string representing the value of the field before the change |
| No | String |
| The identifier of the issue that was updated. Links to a record in the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| Yes | String |
| The value of the field after the change |
| Yes | String |
| A string representing the value of the field after the change |
| No | String |
| 36-character unique site identifier |
Jira issue priority
SQL name for the table: jira_issue_priority
Lists the issue priorities defined in Jira
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| Yes | String |
| The name of this priority |
| No | String |
| Unique identifier of this priority. This is the Primary Key for priority data. |
| No | String |
| The priority identifier within a Jira site. It can be used to associate this record with the priority identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | Number |
| The sequence order of priorities, matching their order of appearance in the user interface |
| No | String |
| 36-character unique site identifier |
Jira issue resolution
SQL name for the table: jira_issue_resolution
Lists issue resolutions defined in Jira
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| Yes | String |
| A description of the resolution status |
| Yes | String |
| The resolution display name |
| No | String |
| Unique identifier of this resolution. This is the Primary Key for issue resolution data. |
| No | String |
| The resolution identifier within a Jira site. It can be used to associate this record with the resolution identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | Number |
| The sequence order of resolutions, matching their order of appearance in the user interface |
| No | String |
| 36-character unique site identifier |
Jira issue status
SQL name for the table: jira_issue_status
Lists the issues statuses defined in Jira
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| Yes | String |
| The name of the status |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | Number |
| The sequence order of statuses, matching their order of appearance in the user interface |
| No | String |
| The category of this status. Links to a record in the |
| No | String |
| Unique identifier of this status. This is the Primary Key for status data. |
| No | String |
| The status identifier within a Jira site. It can be used to associate this record with the status identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| No | String |
| 36-character unique site identifier |
Jira issue status category
SQL name for the table: jira_issue_status_category
Each issue status is associated with a status category.
Lists the status categories defined in Jira
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| Yes | String |
| The color associated with this status category |
| Yes | String |
| The key associated with status category |
| Yes | String |
| The status category name |
| No | Number |
| The sequence order of status categories. To do comes before In progress, which comes before Done. |
| No | String |
| Unique identifier of this status category. This is the Primary Key for status category data. |
Jira issue type
SQL name for the table: jira_issue_type
Lists the issue types defined in Jira
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| Yes | String |
| A description of the issue type |
| No | String |
| Unique identifier of this issue type. This is the Primary Key for issue type data. |
| No | String |
| The issue type identifier within a Jira site. It can be used to associate this record with the issue type identifier in Jira’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| Yes | String |
| The name of the issue type |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| 36-character unique site identifier |
Tables specific to Jira Service Management
There are several tables specific to Jira Service Management data:
Atlassian service refined
JSM affected service mapping
JSM CSAT feedback
JSM incident responder
JSM request type
JSM SLA
Atlassian service refined
SQL name for the table: service
Lists your Atlassian services defined in Jira Service Management and Opsgenie
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | Datetime |
| Service creation time (UTC time zone) |
| Yes | String |
| Service description |
| Yes | String |
| Service name |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String | tbd | Unique identifier of this service. This is the Primary Key for service data. |
|
| String |
| Tier indicating service criticality |
|
| String |
| Service type |
| No | Datetime |
| Service last updated time (UTC time zone) |
| No | String |
| 36-character unique site identifier |
JSM affected service mapping
SQL name for the table: jsm_affected_service_mapping
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String | tbd | Unique identifier of a service. Links to a record in the |
| No | String |
| Unique identifier of an issue. Links to a record in the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| 36-character unique site identifier |
JSM CSAT feedback
SQL name for the table: jsm_csat_feedback
Lists the customer feedback and issue satisfaction data defined in Jira Service Management
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| The identifier of the issue that the CSAT response refers to. Links to a record in the |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
|
| Number |
| Rating given as part of a JSM Issue Satisfaction survey |
| No | String |
| 36-character unique site identifier |
JSM incident responder
SQL name for the table: jsm_incident_responder
Lists the responders to an incident, as defined in Jira Service Management
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| Unique identifier of an issue representing an incident. Links to a record in the |
| No | String |
or
| Unique identifier of the incident responder |
| No | String |
| Type of responder |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| 36-character unique site identifier |
JSM request type
SQL name for the table: jsm_request_type
Lists the request types defined in Jira Service Management
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| Yes | String |
| A description of the request type |
| No | String |
| Associated issue type. Links to a record in the |
| Yes | String |
| The name of the request type |
| No | String |
| Unique identifier of this request type. This is the Primary Key for request type data. |
| No | String |
| The request type identifier within a Jira site. It can be used to associate this record with the request type identifier in JSM’s REST APIs and URLs, but does not guarantee uniqueness across multiple workspaces. |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| 36-character unique site identifier |
JSM SLA
SQL name for the table: jsm_sla
Lists the issue service-level agreements (SLAs) defined in Jira Service Management
Table uses the following columns:
Column | User-generated content? | Data type | Example data | Description |
---|---|---|---|---|
| No | String |
| Indicates whether the SLA was breached. For ongoing cycles, this value may change over time, along with |
|
| String |
| Indicates whether the current SLA cycle is ongoing or completed |
| No | Number |
| Represents the time (in milliseconds) that has passed since the SLA cycle started |
| No | Number |
| Represents time (in milliseconds) taken to complete the current cycle. Only available for |
| No | String |
| Unique identifier of an issue. Links to a record in the |
| No | String |
| Indicates whether the SLA cycle is paused or not. Only available for |
| No | Number |
| Represents the time (in milliseconds) remaining before the expected SLA limit is breached. Remaining times are calculated and updated every 30 minutes. Therefore, the provided value may not represent the actual current remaining time. |
| No | Datetime |
| Last refresh time for this record (UTC time zone) |
| No | String |
| Unique identifier of a Service Level Agreement setting. Use it together with the |
| Yes | String |
| Name of the SLA that the SLA cycle belongs to |
| No | Datetime |
| Start time of the SLA cycle (UTC time zone) |
| No | Datetime |
| Time when the SLA cycle transitioned from |
| No | String |
| 36-character unique site identifier |