Ability to select multiple filters (multiple labels, dates, assignments, etc.) when filtering project tasks

Enhancement Voting Project Management
1

Name of Feature/Request

Advanced Multi-Criteria Task Filtering for Project Boards (Sub-title: Support for multi-select logic across Labels, Assignees, and Dynamic Date Ranges)

Financial, Time Savings, or Quality of Life Improvements

  • Time Savings: Reduces “view-switching” fatigue. Instead of running five separate searches to see tasks for five different team members, a manager can select all five assignees at once, saving an estimated 10–15 minutes of administrative overhead per day, per user.

  • Quality of Life: Drastically improves the usability of the Project Board for Scrum Masters and Project Managers who need to see “the big picture” (e.g., all “High Priority” tasks that are also “Past Due” and assigned to the “Design Team”).

  • Financial Impact: Better visibility leads to fewer missed deadlines. By allowing users to filter for specific bottlenecks (e.g., multiple “Blocked” labels across various dates), projects stay on track, reducing the risk of non-billable overages.

Attempted Solutions So Far

  • Single-Filter Cycling: Manually selecting one label, viewing results, clearing it, and selecting another. This makes comparative analysis impossible.

  • Report Builder Exports: Exporting task lists to Excel just to use the “Filter” function. While effective for data, it breaks the workflow because you cannot move task cards or update statuses directly within a spreadsheet.

  • Browser Search (Ctrl+F): Using the browser search on the board, which is ineffective for tasks hidden in collapsed columns or below the fold.

Digging Deep: The “Why” & Legacy Workflow

  • The “Why”: Modern project management isn’t linear. A task rarely belongs to just one category. We need to be able to see the intersection of data—for example, “Show me all tasks labeled ‘Bug’ AND ‘Client-Facing’ that are assigned to ‘John’.” Without multi-select, we are viewing silos of data rather than the relationships between them.

  • Legacy Workflow (Pre-Striven): In previous tools (like Jira, Trello, or Monday.com), this was accomplished through a “Checkbox” UI within the filter dropdown or a “Query Builder” that allowed for AND/OR logic. It allowed leadership to create “Saved Views” that remained dynamic as the project evolved, ensuring that no task fell through the cracks simply because it didn’t fit into a single, narrow filter category.