nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automated way to set up Hierarchy in Structure plug in

Chappo

Hi,

I have a Program->Product->Initiative->Epic->{Bug & Story & Task} hierarchy, and in structure at the initiative level I am able to automate the structure hierarchy setup by adding an Insert JQL query of "Parent Link" = xxx-55 where xxx-55 is the Initiative that holds all of the epics.

This worked fine when I didn't have many programs and products, I could manually set up the program product hierarchy and do the automation at the lower level.

This view has become quite popular with the business and they wanted to add more and more programs, and maintenance is becoming problematic.

I tried automate higher up in the hierarchy at the program level by "Parent Link" = ppp-5 where ppp-5 is the Program not the Initiative with the hopes that it would build everything all of the way down from there, but it only brought in the products and nothing below. When I do it with the initiative it pulls in all Epics and everything linked to the Epic.

Is there a way to automatically build the hierarchy from a higher level up than what I have now?

Accepted answers

Chappo

I found what I needed. Using extend instead of a query is how you get all of your linked child issues, but this assumes you have Portfolio which I do have installed.

Thanks

All comments

Chappo

I found what I needed. Using extend instead of a query is how you get all of your linked child issues, but this assumes you have Portfolio which I do have installed.

Thanks

Vlad[ALM Works]

Hi Chappo,

Thanks for posting.

Sorry we didn't get back to you in time. Extenders are definitely the way to go! To clarify for others who might not use Portfolio, Structure allows you to easily visualize levels above Epics by Inserting the very first level of your hierarchy (Ex: issuetype = Product). Then you can use the Linked Issues and the Epic Link Extenders accordingly to create the whole hierarchy, provided that you are using Issue Links and Epic Links in Jira:

https://wiki.almworks.com/display/structure/Extend+Generators

Please let me know if you need help with anything else. We can also be reached at support@almworks.com.

Best Regards,

Vlad

ALM Works

Chappo

Hi Vlad, Thanks for the followup and details. That was quite helpful. One quick question. To get what I wanted, (Hierarchy from Program down to Story), I had to add two Extends,

One for Issues belonging to Epics
One for Portfolio child issues.

Is this expected behavior. The Portfolio child issues will not drill all the way down to Story?

Vlad[ALM Works]

Hi Chappo,

You are very welcome!

Yes, this is expected. There are different Extenders which allow you to visualize different types of relationships, based on the link used between the issues (Portfolio Parent Link, Epic Link, Linked Issues etc...). This allows users to have flexibility to build their structures with the desired hierarchy.

You can learn more about Structure's different Extenders here.

Please let me know if you have any other questions.

Best Regards,

Vlad

ALM Works

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

structure

hierarchy