...
These tables rapidly reflect changes in your products, typically within half an hour. This makes them especially useful for custom analysis, or when having the most up-to-date information is important.
All tables in the schema have a workspace_id column. If you have multiple instances of Jira Cloud in your organization, you can use this column to distinguish between them.All tables have row_refreshed_at information that indicate indicates data freshness. It captures the last data refresh time. For example, a timestamp of 2020-12-30T23:00:41.950817Z means that the information in the row is current as of 11 p.m. on December 30, 2020, in the UTC time zone.
Dates and timestamps in the Data Lake are in UTC
Keep in mind that all columns with dates and timestamps (for example, created_at, updated_at, etc) are in the UTC time zone. To convert these to use a different time zone, either change your workspace time zone in your workspace settings or the individual dashboard’s time zone in its dashboard settings.
Workspace data
All tables in the schema have a workspace_id column. If you have multiple instances of Jira Cloud in your organization, you can use this column to distinguish between them.
SQL name for the table: workspace
Lists your Jira instances
Table uses the following columns:
Column | Data type | Example data | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| String |
| 36-character unique site identifier. This is the primary key for workspace data. | ||||||
| String |
| The name of the Jira instance | ||||||
| Datetime |
| Last refresh time for this record (UTC time zone) |
Account data
SQL name for the table: account
Lists the Atlassian accounts within your organization
Table uses the following columns:
Column | Data type | Example data | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| String |
| Atlassian account ID. This is the primary key for account data. | ||||||
| String |
| The name of the account holder | ||||||
| String |
| The email address of the account holder |