# Query relating to the custom filter editors

**URL:** <https://gramps.discourse.group/t/query-relating-to-the-custom-filter-editors/9857>\
**Category:** Help\
**Tags:** filters\
**Created:** [August 16, 2026, 3:33am UTC](https://gramps.discourse.group/t/query-relating-to-the-custom-filter-editors/9857 "2026-08-16T03:33:53Z")\
**Posts on this page:** 1\
**Showing post:** 34

<div class="post-metadata">

**Author:** ![HN1962](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/hn1962/32/9324_2.png) [@HN1962](https://gramps.discourse.group/u/HN1962)\
**Post date:** [August 18, 2026, 7:33am UTC](https://gramps.discourse.group/t/query-relating-to-the-custom-filter-editors/9857/34 "2026-08-18T07:33:16Z")

</div>

Reading through this, several of the pain points here — seeing filter dependencies, testing without reopening the editor, and sharing a complex filter — are exactly what pushed me to build a gramplet of my own, **FilterWorkbench**.

It takes a different angle from FilterParams: it’s built around the _building_ flow, with helper filters as explicit named stages and a live match count that updates as you add rules. The Test button runs the filter in the person view without closing the builder, which is the “test without the useless wide window” itch from the first post.

I’ve written it up in its own thread if anyone wants a look: [Here](https://gramps.discourse.group/t/filterworkbench-a-gramplet-for-building-testing-and-sharing-custom-person-filters/9868)

Not trying to duplicate FilterParams — more a complementary take on the same problem.

---

_[View the full topic](https://gramps.discourse.group/t/query-relating-to-the-custom-filter-editors/9857)._