Hello, community! đź‘‹
By popular demand, we're releasing two new data points to the Atlassian Data Lake: groups and teams.
Group data is stored in the new Group table, which holds the mappings between group IDs and group names.
Team data is stored in two new tables: Team and Team member. The “Team” table holds the mapping between team IDs and team names, and the “Team member” table contains information about which users are part of each team. Note that one Atlassian account could be part of multiple teams.
All the new tables are under the “Organization data” category in the schema browser.
Read more about the new tables and columns.
I recorded a quick video with a couple of examples that show how to create charts using the new tables. The first example shows how to see the number of Jira Software issues each team is working on. The second example shows how to list the Confluence pages that a given group has permission to and what their permission levels are.
You can join your group data and Confluence data to answer questions about page restrictions for a particular group. To do this, you’ll need to join the Group ID column from the “Group” table with the Authorized team column from the “Page restriction” table.
For example, you could create a query to see how many pages are restricted to each group by adding the following columns:
Name from the “Group” table
Page ID from the “Page restriction” table
You can join your team data and your Jira data to get information about teams and their associated Jira issues.
To make it easier to find how many issues are associated with a particular team, we’re actively working to add a new “Team ID” column to the “Issue” table. Stay tuned for this release in the coming months.
In the meantime, you can get this information by joining with the Account ID column in the “Team member” table.
If there are multiple foreign keys in a table that can be joined with the “Account ID” column, make sure you change the query’s join path to use the correct foreign key. For example, if you wanted to know how many issues are assigned to each member of a particular team, you’d need to join the Account ID column with the Assignee account ID column in the “Issue” table under “Jira family of products”.
As mentioned earlier, one account ID can be part of multiple teams, so you may want to filter for a specific team as well.
For new Data Lake connections, these new tables will automatically be available.
For existing Data Lake connections, an organization admin needs to edit the connections. They can edit the connection and save it without making any changes. More about editing Data Lake connections.
Comment below or contact support if you have any questions or concerns. Thanks!
Tina Ling
15 comments