GitHub Projects Bug: Top-Level OR Filters Impede Development Measurement

A project board showing a task incorrectly placed in the 'Todo' column, highlighting a data display bug.
A project board showing a task incorrectly placed in the 'Todo' column, highlighting a data display bug.

Unpacking a GitHub Projects Bug That Impacts Development Measurement

GitHub Projects are powerful tools for tracking work and enhancing developer productivity. However, a recent community discussion highlights a subtle but significant bug that can disrupt project visibility and, by extension, the accuracy of development measurement tools.

The issue, reported by iappwebdev on November 3, 2026, specifically affects board views when their filters contain a top-level OR condition, leading to incorrect item display and misleading column counts during lazy-loading.

The Problem: Misleading Project Board Views

Imagine a GitHub Project board grouped by 'Status' (Todo, In Progress, Done). If you set a view filter like closed:>@today-7d OR no:closed to see recent activity or open items, you expect each column to accurately reflect its status. The bug manifests when you scroll to the end of a column (e.g., 'Todo') to load more items.

Instead of displaying only 'Todo' items, the column count jumps dramatically, and items from other columns—like 'Done' items closed within the last 7 days—infiltrate the 'Todo' column. This visual discrepancy makes it challenging to get an accurate snapshot of project progress, undermining the utility of such development measurement tools.

A reload temporarily fixes the count, but the issue reappears upon further scrolling, causing frustration and hindering efficient workflow.

Behind the Scenes: A Query Parsing Glitch

The core of the problem lies in how GitHub Projects processes the combined filter. The original request sent to the server correctly scopes the query to the column:

GET /memexes/ /paginated_items
  ?after= &q=closed:>@today-7d OR no:closed
  &verticalGroupedBy[columnId]=Status
  &verticalGroupedBy[value]=Todo
  &layout=board

However, the server's evaluation seems to append the column condition (Status:Todo) without proper grouping. Instead of evaluating as (closed:>@today-7d OR no:closed) AND Status:Todo, it's interpreted as closed:>@today-7d OR (no:closed AND Status:Todo).

This misinterpretation means the filter matches:

  • Any item closed in the last 7 days (regardless of its Status).
  • PLUS any open 'Todo' item.

This explains why 'Done' items (if closed recently) appear in the 'Todo' column. The author notes that top-level OR in Projects filters is a relatively new feature (introduced July 16, 2026), suggesting this might be an edge case.

The Simple Workaround for Enhanced Productivity

Fortunately, there's a straightforward solution to restore accurate board views and maintain your developer productivity:

Wrap your entire view filter in parentheses.

So, instead of closed:>@today-7d OR no:closed, use (closed:>@today-7d OR no:closed). This explicit grouping ensures the filter is interpreted correctly, preventing items from appearing in the wrong columns and maintaining accurate counts.

Why This Matters for Development Measurement Tools

While seemingly a minor display bug, such inaccuracies can have a ripple effect. Project boards are often the primary source of truth for team progress. When these views are unreliable, it directly impacts:

  • Decision-making: Managers and team leads rely on accurate status updates.
  • Reporting: Any manual or automated reporting based on these board views will be flawed.
  • Trust in data: Consistent errors erode confidence in the platform as a reliable source for development measurement tools and project tracking.

Ensuring the integrity of project data is crucial for effective team coordination and for any analytics system aiming to provide insights into developer productivity.

A developer successfully using a project board after applying a fix, symbolizing restored productivity.
A developer successfully using a project board after applying a fix, symbolizing restored productivity.

Conclusion

The GitHub community's vigilance in identifying and sharing such issues, along with simple workarounds, is vital for improving platform reliability. By applying this quick fix, teams can ensure their GitHub Projects boards remain accurate, supporting robust development measurement tools and fostering smoother workflows.

|

Dashboards, alerts, and review-ready summaries built on your GitHub activity.

 Install GitHub App to Start
Dashboard with engineering activity trends