In Jira, when I search for a parent issue (e.g., EMP-1
), it appears in the issue navigator, and its linked issues are shown in the Linked Issues field. However, I want the linked issues to appear as separate rows immediately after the parent issue in the search results or exported Word/Excel documents. This grouping would improve visibility and reporting. I’m looking for a solution or workaround to achieve this structured output.
If you are fine to explore a mktplace app to view Issue Hierarchy based on Issue Links, I can suggest our app
The app also allows you to view your project issue hierarchy in a tree view. The hierarchy is created based on your issue inks.You can view %complete progress at each parent level. It roll ups the time tracking fields, story point or numeric fields at each parent level. The app can be added to a dashboard as well
Disclaimer : I am one of the app team member
Hi @Ashok Shembde ,
As it was mentioned before, Jira doesn't allow that out of the box. You can take a look on the app Pivot Report we develop:
You can check this demo report on you own.
It's super easy to customize, any link type works. You can have multiple levels if needed, and even have nested grouping on top of your hierarchy. E.g. by Component and/or Version.
If you need any assistance with the trial or installation, please let me know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ashok Shembde , that isn't possible with native JQL. Obviously you will see the link issues if you click into the one issue. You might consider different add-ons in the marketplace.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.