[Feature Request] Custom views: Globally consolidate cards in a single view based on user-provided filters #911

New Issue

OVERLORD · 2026-02-04T21:37:17+03:00

OVERLORD commented

2026-02-04 21:37:17 +03:00

Originally created by @kerochord on GitHub (Feb 1, 2026).

Which part of the project does this feature apply to?

Frontend

What would you like?

Inspiration

Vikunja's filter feature, and by previous feature requests related to global search (#1478), member-based global filtering (#264) and label-based global filtering (#1439).

Vision

Most Planka feature seem to operate at the Project level (e.g. member filtering, label filtering). While this works well for the majority of use cases, it does prevent users from adopting powerful, cross-project task management flows.

This feature request proposes the introduction of Custom Views. Custom Views would allow users to provide a set of filters (i.e. conditions). Planka would find all applicable cards and show them in a project-like view.

member="kerochord" AND list_name="In Progress" AND label="music"

Challenges

This would be a complex feature to introduce, but it would make Planka very powerful and unlocks lots of new opportunities for power users. These are the challenges I can think about:

Performance: Custom views need to query cards across all projects, which means DB performance and memory usage needs to be taken into account. The search would need to happen server-side. A hard limit on returned cards could be enforced.
Implementing filter conditions: A schema for expressing filtering would need to be introduced. In the most simple approach, it could be introduced as a WHERE clause, (unfortunately?) exposing the DB schema. User provided filtering should be processed server-side for validation and to prevent SQL injection attacks.
UX: Would need to think how to show this in the UI.
- A simple approach could be to continue to groups retrieved cards by project, then 'concatenate' each project views vertically.
- A better though more complex approach could be to introduce a consolidated view of all cards in a single project-like view. Cards could have an indication of which project they belong to. Cards associated with the same list name, regardless of project, could be displayed in a single list.
- Another UX related issue would be ordering. How to sort lists and cards within lists collected from multiple projects?

Originally created by @kerochord on GitHub (Feb 1, 2026). ### Which part of the project does this feature apply to? Frontend ### What would you like? ### Inspiration Vikunja's [filter feature](https://vikunja.io/features/), and by previous feature requests related to global search (#1478), member-based global filtering (#264) and label-based global filtering (#1439). ### Vision Most Planka feature seem to operate at the Project level (e.g. member filtering, label filtering). While this works well for the majority of use cases, it does prevent users from adopting powerful, cross-project task management flows. This feature request proposes the introduction of **Custom Views**. Custom Views would allow users to provide a set of filters (i.e. conditions). Planka would find all applicable cards and show them in a project-like view. ```sql member="kerochord" AND list_name="In Progress" AND label="music" ``` ### Challenges This would be a complex feature to introduce, but it would make Planka very powerful and unlocks lots of new opportunities for power users. These are the challenges I can think about: - **Performance**: Custom views need to query cards across all projects, which means DB performance and memory usage needs to be taken into account. The search would need to happen server-side. A hard limit on returned cards could be enforced. - **Implementing filter conditions**: A schema for expressing filtering would need to be introduced. In the most simple approach, it could be introduced as a `WHERE` clause, (unfortunately?) exposing the DB schema. User provided filtering should be processed server-side for validation and to prevent SQL injection attacks. - **UX**: Would need to think how to show this in the UI. - A simple approach could be to continue to groups retrieved cards by project, then 'concatenate' each project views vertically. - A better though more complex approach could be to introduce a consolidated view of all cards in a single project-like view. Cards could have an indication of which project they belong to. Cards associated with the same list name, regardless of project, could be displayed in a single list. - Another UX related issue would be ordering. How to sort lists and cards within lists collected from multiple projects?

OVERLORD referenced this issue

2026-02-04 21:52:56 +03:00

[PR #911] [MERGED] Add UI Tests using Playwright with BDD #1139

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#911