Hello, I'm trying to apply filter generator to filter issues based on parent's values.
Groups are created by popping up the values from the story level to an epic by aggregate function. Then I want to keep stories only related to the group to do that I'm using parent{} function to get value from grandparent and comparing it with a story. It works great in quick transformation, however the same code doesn't work if you try to apply it via automation.
Here is the code:
parent#level=-2{item} == groupValue
where groupValue returns the name of the group the item belongs.
What I have now:
- Group 1
-- Epic 1
--- Story 1 (Related to Group 1)
--- Story 2 (Related to Group 2)
- Group 2
-- Epic 1
--- Story 1 (Related to Group 1)
--- Story 2 (Related to Group 2)
What I want to get:
- Group 1
-- Epic 1
--- Story 1 (Related to Group 1)
- Group 2
-- Epic 1
--- Story 2 (Related to Group 2)
Hello @Sasha ,
Welcome to the Community!
The reason your Filter will work as a Transformation, but not as a Generator is due to the order of operations for Generators.
Filtering happens before Grouping. So, as a Generator, the filter is unable to reference the Group, because it has not happened yet. Transformations happen after all generators, which is why it does work there.
There is a workaround you could try.
You can create a new structure and use the Structure Inserter as your Insert Generator. Select the original structure as the one you want to insert. From here, you can now add your FIlter by Attribute w/ Formula as a Generator.
Please let me know if this helps, or if I can clarify anything!
Best,
David
Hi @David Niro
Thank you for the fast reply. I tried the workaround you proposed. However, the issue still remains. Filter w/Formula works fine as a quick transformation, but if you move it to generators, it stops working.
Might it be related to adding one more level of depth when the "Automation" mode is enabled?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Sasha ,
That is very possible. When Automation is enabled, it counts as a level. So, the level the calculation is being made on will be different when Automation is enabled vs when it is not.
If you still encounter issues after adjusting this, please feel free to contact our support team directly via support@almworks.com or through our customer portal support.almworks.com. We can review some screenshots and advise on what may need to be adjusted.
Best,
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.