Hi community!
Jira Board related tables, Jira Filters table and a new 'Activated at' column in the Sprint table are now available in Analytics and data share. These additions make it possible to understand Jira Board attributes, Board - Project relationships, and the actual moment a Sprint started.
For Analytics, the following new tables and column are available:
‘Board’ table - Board key attributes (name, type, ID, location), under Jira schema
'Board columns' table - Column configuration for each board, under Jira schema
‘Board filtered project mapping’ table- Maps Boards to the Projects, under Jira schema
‘Filters’ table - Your saved searches in Jira, under Jira Family of Apps schema https://support.atlassian.com/jira-software-cloud/docs/save-your-search-as-a-filter/
‘Activated at’ column in existing Sprint table - The actual timestamp when a sprint was started ( i.e. when someone clicked "Start Sprint" https://support.atlassian.com/jira-software-cloud/docs/plan-a-sprint/ )
For data share, the following new tables and column are available:
jira_board table
jira_filter table
activated_at column in jira_sprint table
The new data is rolling out gradually in the coming 1-2 weeks.
For Analytics, the ‘Board’ and 'Board columns' tables contain key attributes and descriptions about each board.
‘Board ID’ - is the unique identifier of the Board. It can join with ‘Original board ID’ from Sprint table where the sprint was originally created. This doesn't always mean the sprint started on this board, as sprint can start on a different board.
‘Board type’ - when ‘Board type’ is ‘SIMPLE’, it means this board is from a Team-managed Project.
About Board location - There are 2 columns indicate where a Board is located.
‘Board filter ID’ - This column is the Jira filter id that is associated with the Board. It can join with ‘Filter ID’ from the new ‘Filters' table.
‘Sort order’ - is the order the column will appear on the Board, in ascending order.
‘Status config sort order’ - is the order that the status will appear in the column’s status list, in ascending order.
For data share, all above information is stored in jira_board and jira_filter tables.
For Analytics,
Board<>Project mapping - ‘Board filtered project mapping’ table shows which Jira Projects are included in which Boards. Company managed project can be in more than one Board. The table flattens out the many-to-many relationship.
Board<>Sprint mapping - Directly on Analytics, you can only get the Sprints that are originally created on a Board. This is using ‘Original board ID’ from Sprint table joining Board table. There is no direct way to see current Board and Sprints and Work Item map. The ‘Saved jql’ value from ‘Jira Filters’ table can provide more context for that.
This column is a new data point from Jira cloud. The data started to be collected from March 9 - 13, 2026. For Sprints that were already active or closed before this date, ‘Activated at’ column was retrospectively populated with the ‘Projected to start at’ value, meaning the two columns will match for those historical sprints.
On Analytics:
For new Data Lake connections that include Jira data, the new tables and the new column will automatically be available.
For existing Data Lake connections, an organization admin need to edit and save the connection. If the connection already includes Jira data, the organization admin can edit and save it without making any changes to pick up the new tables. More about editing Data Lake connections.
On data share, the new tables and column will automatically be available.
Comment below or contact support if you have any questions or concerns. Thanks!
Tina Ling
1 comment