Structure Board: Loop Child Issues under an Epic

Arul A_ Joseph Raj
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 5, 2024

Hi All,

We use Structure extensively. Recently, we moved from JIRA native hierarchy to custom hierarchy (Initiative -> Epic -> Feature -> Story/Task -> Sub-Task). After the move, Epic panel available in the Backlog became Feature.

Now, I am trying to replicate the Epics panel using Structure where only Epics will be listed from multiple JIRA projects will be listed. No parent or child issues. View is expected to have Key, Summary, Progress, Status, Resolution, Team, #of Features, #of Features Completed, Related Epics.

Related Epics is a formula column which displays concatenated values of Key + Summary of epics linked through "relates to" link using issueLinks.

We use Structure transformation "Child Issues from Advanced Roadmap" to display children on demand. There are no issues with the formula in populating the #of Features and #of Features Completed columns when child/children rows are available.

Problem is, I would like to loop all child issues, Features, and sub-tasks, of an Epic to get the count by features and the count by feature status when "Child Issues from Advanced Roadmap" is not used and only epics available.

I might be missing something here. Need help with the formula. Any help would be greatly appreciated.

Best Regards,
Arul

2 answers

Suggest an answer

Log in or Sign up to answer
2 votes
Stepan Kholodov _Tempo_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 5, 2024

Hello @Arul A_ Joseph Raj 

In general, the Formula column only considers values of issues that are present in the structure. So when you disable the Extend transformation and the issues disappear, it's normal for the formula to lose data since its origin disappears.

You can try a different approach here: use the Extend generator instead for adding the child issues in the core of the structure, and using a Filter transformation for hiding the child issues (and disabling it when you need to see the full hierarchy). In this case, the origin data for columns will remain in the structure at all times even if the Filter transformation is enabled.

I hope this helps. If you need further assistance, please reach out to us directly at our support portal.

Best regards,
Stepan
Tempo (the Structure app vendor)

0 votes
Valerie Knapp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 5, 2024

Hi @Arul A_ Joseph Raj , welcome to the Atlassian Community and thanks for your question!

Please reach out to the vendor for helo with Structure. In my experience, they are super responsive and helpful  -https://marketplace.atlassian.com/apps/34717/structure-by-tempo-jira-portfolio-management-ppm?hosting=datacenter&tab=support 

Hope this helps.

Cheers

TAGS
AUG Leaders

Atlassian Community Events