More issue hierarchy data! - Expect partial parent data over the next two weeks

[#1]

What’s happening

Our team is in the process of adding data from the “Parent link” custom field used in Advanced Roadmaps for Jira into the “Parent” field that you can access in the Atlassian Data Lake. This means you’ll be able to report on and roll up to levels of hierarchy higher than epics!

As we’re rolling out these changes and the data becomes available, you may experience partial data when querying the “Parent” field in Atlassian Analytics. For example, you may see the parent for one epic but not another.

The rollout starts today and will take about two weeks to complete.

Sept. 25, 2023 update: We hit a few road bumps with the rollout. We now anticipate the rollout to be completed around October 6, 2023.

The rollout to add more parent data is completed! The new "Parent issue ID" column will be available later in October.

Coming soon: New “Parent issue ID” column

With more issue hierarchy data becoming available, we want to make it easier and faster for you to pull this data for parent-child relationships. To do this, we’re going to introduce a new “Parent issue ID” column to the “Issue” table in the “Jira family of products” schema. This column will contain the immediate parent ID of an issue.

We plan to release this new column around the time that the rollout is complete.

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

[Marwan Saab]

Awesome news! This will surely make hierarchical reporting far more comprehensive and efficient.

Just curious, are there any updates on including the "Team" field in the Atlassian Data Lake as well?

Keep up the great work!

Cheers,
Marwan

[Tina Ling]

Hi Marwan,

I assume you mean 'Jira team'.  Adding Jira team's data into the Data Lake is in our radar.  Here's the feature request ticket for 'jira team'.  You can upvote and watch this ticket. 

Thank you for the comments, please keep them coming.   

Best,
Tina

[Marwan Saab]

Thank you Tina - I have just voted on that ticket!

I mean the "Jira Advanved Roadmap shared Teams" data.

I know that at the moment there is work to move the "Shared Teams" outside of JAR (https://community.atlassian.com/t5/Advanced-Roadmaps-articles/Teams-in-Advanced-Roadmaps-What-s-changing-and-what-you-need-to/ba-p/2259096) - having said that, I feel that the sooner we get that data in the data lake, the better.

Please note that I have already implemented a workaround to get the missing JAR data in the data lake (combination of Hidden Fields and Jira Automation) - however, that solution is not scalable!

Thank you again.

Cheers,
Marwan

[Andrew Furlong]

Hi, 

I'm not seeing the parent link field in my data schema - is there any reason why this might not be working? Thanks!

[Tracy Chow]

Hi @Andrew Furlong , this article talks about how to get the new "Parent issue ID" column: https://community.atlassian.com/t5/Atlassian-Analytics-articles/New-column-to-make-issue-hierarchy-queries-easier/ba-p/2513488 

If the Atlassian Data Lake connection already includes Jira data, the organization admin can edit the connection and save it without making any changes to get the new column.