I would like to create a standard hierarchy in structure, where I can see only epics and the features within the epics.
I have used the automation "Insert" (epic and features in specific project) and "Group" via Epic.
But I can see also epics from another project in my list and in "No epic" folder the epics again.
How can I avoid it?
Looking forward to your answer.
There are several ways to approach this.
1. You can use an Inserter to add all Epics and then use an Extender to pull in Features under these epics. The only drawback here is that you won't see Features without Epics.
2. You can pull in Features using the Inserter and then group them by Epic like you did. But in this case you won't see the Epics which have no Features.
3. Lastly you can use the new Duplicates Filter (available in 3.3.2) to show a structure with all Features and Stories:
So you need to insert all contents of the board like you already did, then Extend epics with stories and then add the Duplicates filter, which will make sure that features are not shown on the top level if they've been added under some parent.
I hope this helps.
Thank you for your fast response, unfortunately I haven't informed about it:(
I thing we will go for the 1. approach, because we are able to see the features in the no epic folder :) We can still see the epics from another projects, but it is not so bad.
In the second option we see all issues within the epic, but we would like to exclude it only to features.
And to the 3. point, we still have JIRA 6.3, so after the upgrade, I will try this proposal too.
Hello! My name is Genevieve Blanch, and I'm the Marketing Manager at RefinedWiki, creators of apps to give teams the tools to customize Atlassian platforms. Currently, 44% of the tech team at Re...
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