The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

New column to make issue hierarchy queries easier

 

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!

How to get the new column

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

🎥 Video example using the new column

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.

🔖 Updated knowledge base article

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.

Tell us what you think

Comment below or contact support if you have any questions or concerns. Thanks!

0 comments

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

TAGS
AUG Leaders

Atlassian Community Events