we have a hierarchical issue type structure like Type A , Type B and Type C
I would like now to create a structure where I can group the issues by likes in the way that I have on the top layer all issues with issue type A and underneach all issues with type B that are linked via any link to the issue type A and in the third layer all issue from Type C that are in any way linked to the issues of typ B in the secound one.
Anyway I only see that one can group the issues by a specific link type and since the types are not all the same I never have the complete picture visible in the structure. Is there any way I can achieve this?
all the best
Hello @Lars Ulrich Krieg ,
David from ALM Works here. Welcome to the community!
If I understand correctly, you are using our product, Structure for Jira, and would like to build a hierarchy that Shows
If I have it right, please reach out to our customer support team directly via email firstname.lastname@example.org or through our customer portal support.almworks.com. We will be happy to review your use case in more detail.
Hello @Lars Ulrich Krieg ,
With that said, I do recommend contacting our support team to review all of the details of your use case in order to build a solution that makes the most sense.
It will required an app to do that.
Structure for JIRA, Big Picture or Advanced Roadmap.
With the 2 first you can define hierarchy based on links and display it within the app.
With the last one you can define the hierarchy in the app and use Parent Link to reference the parent issue in order to display it in the roadmap.
I've miss the "any link". I' m not sure you can.
Maybe you can set an automation or a listener if you have scriptrunner to create a link you will use to do the hierarchy everytime a link is created.
Then in a Structure, list all issues of type A, extend with the link you created, filter issue of type B (at the current level only or manually and set the level number (1 or 2)) then extend and filter again but on type C this time.
If you defined a hierarchy with type, A, B, C why you don't define the link to use ?
I'm aware of that option. Anyway it is not scalable since if there is a new link type I have to rework the extent generators in my structure.
Let me change the question slightly. How do you recommend to build up a structure that can be used as a basis for the gantt chart? Maybe I'm just using the wrong approach here.
All the best
That way we can more easily have a dialog about your use case(s) and give you the best possible advice.
We want to help you be successful. :)
Thanks for pitching in, @Florian Bonniec 👍
If you are fine with a marketplace app, you can try out our add-on to get this data
The app provides the following features.
- View the full Jira Issue Type hierarchy of Linked issues,
Portfolio/Advanced Roadmaps, Epics, and Subtasks up to 10 levels.
- % complete based on time spent and story points at each hierarchy level
- Sum up Time Spent, Org Estimate, Time Rmng, custom number