I have a report which shows a table of issues that can be filtered on Epic Link.
Within a given epic I have Stories and sub-tasks - however, when filtering on Epic Link, I can only drill down as far as Story level.
In the example below Story ISD-523 has a sub-task - there is an icon to expand - but you cannot expand any further (if you see what I mean).
So, how can I filter on Epic Link all the way from the top to the bottom of the tree?
Is it because sub-tasks do not inherit the Epic Link of the parent Story? Is there a way around this?
yes, you are quite right - it is because of sub-tasks do not inherit the Epic Link of parent Story. I could not imagine how to avoid this restriction using Epic Link dimension as a Page filter.
Issue dimension Epic hierarchy Epic level members are the same as Epic link members. Therefore, as a workaround, you could create a calculated measure returning the Epic level issue name for all Issue dimension Epic hierarchy level members (from epic itself to sub-tasks) and then filter by this column to get only particular epic with all its stories and subtasks.
The calculation for such a measure could be the following:
CASE WHEN [Issue.Epic].CurrentMember.Level.Name matches 'Epic|Parent|Sub-task' THEN Ancestor([Issue.Epic].CurrentMember, [Issue.Epic].[Epic]).Name END
For more detailed assistance, please, contact support@eazyBI.com .
eazyBI Customer Support Consultant
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs