I’m running into a problem with the filtering and viewing logic.
I created a Kanban boards section and configured a separate board for each team, with individual board-level filters.
However, these settings do not apply to the “List” view. As a result, users are forced to configure the “List” view individually for each employee, and the “List” view does not inherit the board’s global filters.
If inheriting the board filter is not supported by design, then this is fundamentally inconsistent and highly counterintuitive: the board’s global filter is supposed to define the scope of work for that board/team. But in practice, simply switching to a more convenient view (“List”) effectively ignores that scope and exposes a much broader set of issues. This defeats the purpose of having a board-level filter and forces teams to create and maintain separate per-user views just to replicate the same scope, which is unnecessarily complex and inconvenient.
In practice, this makes the List view very inconvenient and almost unusable for team-wide workflows. In other products (e.g., Asana, Notion), I can save a view and its filters at the project/space level so they apply to everyone. Even Plane handles this more conveniently.
Please consider improving this in one of the following ways:
**Option A (preferred):** make the “List” view inherit the board’s global filter (configured once and works for everyone).
**Option B:** allow saving and assigning a shared List view for a team/project, while keeping personal per-user customization as an option.
I would appreciate your feedback on this and any indication of whether/when this could be addressed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.