Reusable/Shared Workflow Filters (Copy or Template-Based)

Problem:
Currently, filters have to be built individually within each workflow. When multiple workflows need the same filtering logic (e.g., excluding certain ticket types, board statuses, or client segments), there's no way to reuse that configuration — each one has to be recreated manually. This makes maintaining consistency across workflows time-consuming and error-prone, especially when a filter rule needs to change and has to be updated one workflow at a time.

Requested Solution (in order of preference):

Filter Templates (preferred): Allow filters to be created as standalone, reusable templates that individual workflows can "subscribe" to. If the template is updated, all subscribed workflows automatically inherit the change — similar to how a shared component or config would propagate. This would be the most efficient long-term solution for keeping filter logic consistent across many workflows without manual re-entry.
Copy Filter from Another Workflow (minimum viable option): At minimum, add the ability to copy an existing filter configuration from one workflow into another when creating or editing a workflow. This wouldn't keep them in sync going forward, but would eliminate the need to rebuild identical filters from scratch each time.

Why this matters:
As the number of workflows grows, so does the overhead of keeping filter logic aligned across them. A subscription-based template model would significantly reduce maintenance time and reduce the risk of drift/inconsistency between workflows that are supposed to behave the same way.