You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
At the beginning of September, we announced we’d add more issue hierarchy data into the Atlassian Data Lake. We also said we’d add a new column to the schema to make querying parent-child relationships easier. Now that the rollout of issue hierarchy data is done, we’re excited to share that the new Parent issue ID column is ready to use!
Starting today, all new Data Lake connections that include Jira data will have the new “Parent issue ID” column in the “Issue” table in the “Jira family of products” schema.
For existing Data Lake connections, an organization admin needs to edit the connections. If the connection already includes Jira data, the organization admin can edit the connection and save it without making any changes. Read about editing Data Lake connections.
Check out this video tutorial from Inder, one of the Product Managers for Atlassian Analytics, where he shows how to use the new “Parent issue ID” column to get a list of all issues that are in an epic.
We’ve updated our existing knowledge base article with an example of how to use the new column. Bookmark the page so you can refer to it when you need it.
Comment below or contact support if you have any questions or concerns. Thanks!