4 min read • Guide 451 of 877
Creating Effective Filtering Systems
Effective filtering transforms an overwhelming backlog into a focused view of exactly what you need to see. GitScrum's label system, saved views, and powerful filtering capabilities help teams organize work into meaningful categories and quickly find relevant tasks without scrolling through hundreds of items.
Filter Strategy by Role
| Role | Primary Filters | Saved Views |
|---|---|---|
| Developer | Assignee: Me, Sprint: Current | My Tasks, In Review |
| Tech Lead | Label: Blocked, Priority: High | Blockers, Tech Debt |
| PM | Sprint: Current, Status: All | Sprint Progress, At Risk |
| Manager | Project: All, Assignee: Team | Team Overview, Capacity |
Designing Your Filter System
FILTER HIERARCHY
┌─────────────────────────────────────────────────┐
│ │
│ Level 1: Project/Board Selection │
│ └── Which project(s) to view? │
│ │
│ Level 2: Time Context │
│ └── Which sprint/milestone/date range? │
│ │
│ Level 3: Status Context │
│ └── Which columns/workflow stages? │
│ │
│ Level 4: Ownership │
│ └── Whose work? Assignee/Reporter/Team │
│ │
│ Level 5: Classification │
│ └── Labels, priority, type, epic │
│ │
└─────────────────────────────────────────────────┘
Essential Saved Views
VIEW: MY FOCUS TODAY
┌─────────────────────────────────────────────────┐
│ Filters: │
│ • Assignee = Me │
│ • Sprint = Current │
│ • Status ≠ Done │
│ • Priority = High OR Due Today │
│ │
│ Sort: Priority DESC, Due Date ASC │
└─────────────────────────────────────────────────┘
VIEW: TEAM BLOCKERS
┌─────────────────────────────────────────────────┐
│ Filters: │
│ • Label = Blocked OR Status = Blocked │
│ • Sprint = Current │
│ │
│ Sort: Days Blocked DESC │
│ Group by: Assignee │
└─────────────────────────────────────────────────┘
VIEW: READY FOR REVIEW
┌─────────────────────────────────────────────────┐
│ Filters: │
│ • Status = In Review │
│ • Assignee ≠ Me │
│ │
│ Sort: Updated DESC │
└─────────────────────────────────────────────────┘
VIEW: TECH DEBT BACKLOG
┌─────────────────────────────────────────────────┐
│ Filters: │
│ • Label = Tech-Debt │
│ • Status = Backlog OR To Do │
│ │
│ Sort: Impact Score DESC, Age DESC │
│ Group by: Component │
└─────────────────────────────────────────────────┘
VIEW: CLIENT-FACING PROGRESS
┌─────────────────────────────────────────────────┐
│ Filters: │
│ • Label = Client-Visible │
│ • Sprint = Current OR Last 2 Sprints │
│ • Status = Done OR In Progress │
│ │
│ Sort: Completed Date DESC │
└─────────────────────────────────────────────────┘
Filter Combinations
POWERFUL FILTER PATTERNS:
Find stale tasks:
┌─────────────────────────────────────────────────┐
│ Status ≠ Done │
│ AND Updated > 7 days ago │
│ AND Sprint = Current │
└─────────────────────────────────────────────────┘
Find at-risk items:
┌─────────────────────────────────────────────────┐
│ Due Date < 3 days │
│ AND Status ≠ Done │
│ AND Status ≠ In Review │
└─────────────────────────────────────────────────┘
Find unassigned work:
┌─────────────────────────────────────────────────┐
│ Assignee = None │
│ AND Sprint = Current OR Next │
│ AND Priority = High OR Medium │
└─────────────────────────────────────────────────┘
Best Practices
- Create personal AND team saved views for different contexts
- Name views clearly with context (My Tasks Today, not View 1)
- Limit default view complexity to essential filters
- Use filter shortcuts for frequently accessed combinations
- Share useful views with team for consistency
- Review and prune saved views quarterly
- Combine with grouping for better visualization
- Default to current sprint unless historical view needed
Anti-Patterns
✗ Too many filters making results empty
✗ No saved views (recreating filters daily)
✗ Team using inconsistent filter definitions
✗ Filters that hide important information
✗ Over-complex views that confuse more than help
✗ Never updating saved views as workflow changes