Creating a filter or table

[Gaston Motola]

I have Epic A and then I have Epic B that lives inside Epic A (they link to each other).

Epic A has two date fields that I want to show on the filter/table/dashboard.

What I want to do is to have a dashboard that shows the Summary (name) of Epic B and that it also shows the two date fields from the parent Epic A. 

I think I managed to do it once a long time ago, I can't find it, I really appreciate the help on this. Thanks.

[Ted Nieblas]

Hi @Gaston Motola

An issue link does not work the same as the Parent/Child relationship in Jira. The existence of an issue link (of any type) does not make it behave as if it lives inside the other. This is likely why you are using issue links as Jira will not let you define an Epic as a child to another Epic as it does not follow the issue hierarchy.

If this is a must have requirement, I would create custom date fields and update them using automation between Epic A and Epic B using the Linked Issues branch type.

[Gaston Motola]

Thanks for the reply. Any pointers on how can I do that last part? I can request the custom date fields on Epic B, but how would I go about automating the "copy dates from Epic A into Epic B"? They need to be in synch at all times. Any pointers on what should I be looking for this? Thanks.

[Hannes Obweger - JXL for Jira]

Hi @Gaston Motola,

if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of advanced features, including support for configurable issue hierarchies. These issue hierarchies can be based on Jira's built-in parent/child relationships (like Task/Sub-task, or Epic/Story), and/or based on issue links of configurable issue link types.

This is how it looks in action:

In the above hierarchy, "sub-epics" WORK-148 and WORK-146 are connected to their parent epic WORK-431 via issue links.

You can view any issue fields in your JXL sheet, so it's easy to have both the parent summaries and the children date fields on the same screen. I should also add that issue hierarchies can easily be combined with JXL's other advanced features, such as issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes