How to list Epic and all issues linked to it?

[Jussi Soro]

I am looking for a way to list in (kanban) board column all epics that are in that status somehow grouped together with all the issues that are linked to them.

The use case is that when an order for a feature is made, PM creates an epic for the feature and they also create requirements for that epic (each requirement in their own issue). Requirements are linked to Epics with issue links rather than parent-child link, because one requirement may be linked to many Epics.

How would I achieve this? 

The optimum outcome would be that there would be swimlanes for each epic which list the epic as a card and also all requirements that are linked to it.

As the Epics keep changing all the time, I can't use static epic key to achieve this. 

What would be the JQL to achieve this?

[Dmitry Astapkovich _Colined_]

That sounds more like a custom report, since Jira is not really good with using links as a source in search. E.g. you can search for issues of the certain type from the specific project OR issues with links of a specific type. 

If you are ok to use Marketplace Apps, take a look on Pivot Report we develop:

As you can see on the screenshot, we can define custom hierarchy using issue links. And then we can extend the initial search results with parent and child issues if needed. Another thing is that you can set grouping via rows to whatever is needed with up to 5 level. E.g. It could be Epic link, then Assignee and Issue Type.

You can check demo report here. 

[Bill Sheboy]

Hi @Jussi Soro 

Short answer: as you have described the configuration, that is not possible.

You describe using Issue Links rather than the parent / child relationship for the Epics and their child issue, "requirements".  And that multiple Epics can link to the same requirement.  An issue cannot be displayed on a Jira board multiple times, making it impossible to show Epic swim lanes with the Linked Issues below them.  A workaround to that would be to instead add the Linked Issue keys to the Epic card details on the board.

What do the "requirements" represent? 

• If they are work-to-do, why wouldn't there be separate requirement issues for each parent Epic?  That would immediately solve the problem because the parent / child linkages could be used.
• If they do not represent work, consider using other ways to represent them for each Epic, such as checkboxes, labels, etc.

Kind regards,
Bill