Show field value from grand parent item in Structure

[Mathias H_]

Hello,

We have an item hierarchy like this:
1. Initiative
  1.1 Epic 1
    1.1.1 Feature 1
    1.1.2 Feature 2
  1.2 Epic 2

When I look at my Feature list, I need the overall priority from the Initiative shown for each feature. This is a field value on the Initiative item.

With this code, using the Formula language, I have been able to show field values from the parent of the Features, the Epic:
WITH _format(issue) = """${issue.Summary}""" :
issuelinks
.filter($.type.inward="is implemented by")
.filter($.source=this)
.MAP(_format($.destination))

But, I need to get one step higher, and reach the parent of the parent. Tried nesting the WITH statement, but I cannot get the code working...

Anybody have succeeding with something like this, or have ideas to the solution?

[Stepan Kholodov _Tempo_ · Accepted solution]

Hello @Mathias H_ 

If all issues - Initiatives, Epics and Features - are added to the structure and organized in a form of a hierarchy, then you can display the Priority of a parent Initiative for each feature with this formula:

if issuetype = "feature": parent{if issuetype = "initiative" : priority}

but if only Features are present in the structure then it's not possible. You can extract a value from a linked issue without adding it to the structure, but the issueLinks Formula function can only reach to issues that are linked directly to those that are on the structure. So you would need to at least add Epics to the structure above Features - then you can extract Priorities of Initiatives for their linked Epics and display the values for Features.

I hope this helps. If you need further assistance or have other questions, please reach out to us directly at our support portal and we'll get back to you shortly.

Best regards,
Stepan Kholodov
Tempo (the Structure app vendor)

[Mathias H_]

Hello @Stepan Kholodov _Tempo_ 

Thank you very much for the answer! Not the one I was hoping though ;).

I would like to keep my feature view efficient and avoid having many levels that I need to click on to open. 

I have a grouping already in the structure - representing my priority "Now", "Next", and "Later", with all my features below those.
So I really wanted to just have a column with the data from the grand parent, so the portfolio data was immediately visible without needing to also have the parent added to the tree.

But I tried your suggestion and it definitely works, even though the data is "hidden" away in a tree structure. So again, thanks for that.

Best regards,
Mathias