## Overview This epic introduces enhanced status filtering capabilities across GitLab's work item ecosystem by implementing "is one of" filtering functionality. Currently, users can only filter by a single status at a time, which limits their ability to efficiently view and manage work items across multiple status states. ## Problem Statement Users currently face limitations when filtering work items by status: - Only single status filtering is available across issues, work items, and issue boards - Users cannot efficiently view items across multiple related statuses (e.g., "Needs triage" AND "Confirmed") - This creates a gap between current label-based filtering capabilities and status-based filtering ## Solution Implement "is one of" status filtering that allows users to select multiple status values simultaneously, enabling more flexible and powerful filtering across: - **Issues** - Enhanced filtering on project and group issue lists - **Work Items** - Multi-status filtering on work item lists - **Issue Boards** - Advanced filtering capabilities for legacy issue boards ## Design Reference The filtering interface follows the established design patterns: https://gitlab.com/gitlab-org/gitlab/-/issues/383125/designs/Filters.png ## Scope & Deliverables ### Issues & Work Items - **Frontend Implementation**: Multi-select status filtering UI components - **Backend Implementation**: API support for multiple status filtering parameters - **Integration**: Seamless filtering experience across project and group work item lists ### Issue Boards - **Legacy Board Support**: "Is one of" filtering for existing issue board functionality - **User Experience**: Maintains consistency with current filtering patterns ## Success Criteria - [ ] Users can select multiple statuses using "is one of" operator - [ ] Filtering works consistently across issues, work items, and issue boards - [ ] Performance remains optimal with multi-status queries - [ ] UI/UX follows established GitLab design patterns ## Timeline **Target Milestone**: 18.7 (December 2025) - **Development Period**: November 15 - December 12, 2025 - **Release Date**: December 18, 2025 ## Related Work This epic builds upon GitLab's custom status functionality and addresses user feedback about filtering limitations compared to label-based workflows.