Filtering a selected item should not cause its children to also be filtered
Filtering a selected item should not cause its children to also be filtered. I tried filtering a selected item that had children and was expecting everything but the item and its children to be removed. However, applying the filter removed all child items, which essentially renders the filtering feature not very useful.
Alex M.
shared this idea
-
David Niro (Customer Support, ALM Works) commented
Hello Alex,
David from the ALM Works Customer Support Team here!
Have you tried adjusting the Generator Scope to Filter on the level of your parent issue?
When creating a Filter Generator, or Quick Filter, you have the option to define the Level it is applied to. It may be that you have this set to FIlter on "all levels" or possibly on the child level.To check if this is the case, double click on the filter generator, or the edit option if you are using quick filter transformation. Next, review the "apply to level" option. If your parent issue was added by the Insert Generator, you will want to set the level to 1. Depending on how your structure was built, it may be on a different level though.
If you already tried this and it's not working, or if you would like to review in more detail, please send an email to support@almworks.com and we can set up a time for a screen share to gather additional information!
We look forward to hearing from you!
Best Regards,
David Niro
www.almworks.com