Connect your data to Atlassian Analytics
Learn how to connect and manage your connected Atlassian data and external data.
Atlassian Analytics is in an early access program
Only people who are part of this invite-only early access program have access to Atlassian Analytics.
Schema for Jira Software
In addition to the tables for the Jira family of products, Jira Software has extra tables added to the Atlassian Data Lake schema.
Columns with an asterisk (*) are only available when you include all data for your products in a Data Lake connection. Learn more about how to set the scope of data for Atlassian Data Lake connections.
JSW issue estimate history
The jsw_issue_estimate_history table tracks changes in issue estimate data over time. Specifically, it tracks changing in Jira’s Original Time Estimate field or fields that have “story point” in their name.
Arbitrary custom fields configured in Jira Software boards are not yet supported.
The table uses the following columns:
author_account_id* (string)
The unique identifier of the person who updated the issue estimate
ended_at (datetime)
The time (UTC time zone) when the new field value was replaced by another
It is NULL if there was no subsequent change.
estimate* (number)
The issue estimate after the change
field_id (string)
The unique identifier of the estimate field
field_name* (string)
The name of the estimate field that was updated
issue_id (string)
The unique identifier of the issue that was updated
It links to a record in the jira_issue table.
prev_estimate* (number)
The issue estimate before the change
started_at* (datetime)
The time (UTC time zone) when the new estimate value was assigned
time_in_estimate_secs (number)
The time interval (in seconds) between the start and end time of the estimate value captured by this record
It is NULL if there was no subsequent estimate change (in other words, the new estimate is the current one).
workspace_id (string)
An Atlassian identifier that maps data to a site in the workspace_info table
JSW issue sprint history
The jsw_issue_sprint_history table tracks changes in issue allocation to sprints over time
It uses the following columns:
action (string)
Indicates whether the issue was added or removed from a sprint
Possible values: added, removed
action_at (datetime)
The time (UTC time zone) when the issue was added or removed from a sprint
author_account_id* (string)
The unique identifier of the person who changed the issue allocation to a sprint
issue_id (string)
The unique identifier of the issue that was allocated to a sprint
It links to a record in the jira_issue table.
sprint_id (string)
The unique identifier of the sprint that the issue was added to or removed from
workspace_id (string)
An Atlassian identifier that maps data to a site in the workspace_info table
Was this helpful?