Hello all,
First of all, I want to express my appreciation for the assistance of the community; I am truly grateful.
I've created a structure with a simple insert of JQL grouped by Epic. However, within this structure, I've noticed a "folder" labeled "No Epic" under which other Epics appear duplicated. I'm crafting this structure with CurrentUser() in mind, so manual amendments are not a preferred method of handling this issue.
Is there a way to view Epics, stories, tasks, etc., in a hierarchy without encountering duplicates under "No Epic"? Please note that I am using single JQL inserts, not multiple inserts that would create duplicates.
Thank you for your insights; I'm still learning.
Have a great day!
Hello @Miroslav Sochor
The 'No epic' group is created for all issues that don't have values in the Epic Link field, which includes the Epics themselves. To avoid that, you can try a different approach of building the structure without using the grouper:
1. Add the Epics(and other issues that should be present on the top level of the structure) by the Insert generator.
2. Add the Stories Under Epics Extend generator for adding issues of Epics under them.
Also, please note - if your goal is for different users to see only issues that are assigned to them in the same structure, the currentUser() JQL function used in generators will not give you such results. Generators always run from under the structure's owner and they will only show issues of that user. If you want to filter the structure out for each user individually, do this instead:
1. Build the structure with generators to show it in full with issues of all relevant users.
2. Use the Filter transformation with the currentUser() JQL function. The filter will be applied on top of the generated content, and only issues of the viewing user will be displayed.
I hope this helps. If you need further assistance or have other questions about Structure, please reach out to us directly at our support portal.
Best regards,
Stepan
Tempo (the Structure app vendor)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.