Projects board: lazy-loading a column returns items from other columns when the view filter contains a top-level OR #211995
Unanswered
iappwebdev
asked this question in
Projects and Issues
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Projects
Body
Summary
In a board view whose filter contains a top-level
OR(without parentheses), scrolling a column to the end loadsthe next page of that column from
paginated_items. The server returns items that do not belong to the column(closed items with a different Status), so the column count jumps and closed items show up in the wrong column.
Steps to reproduce
closed:>@today-7d OR no:closed.Todothan fit on the first page, and several items closed within the last 7 days with StatusDone.Todoshows the correct count (here: 40).Todocolumn to the end so that the next page is loaded.Expected
Todokeeps its count (40) and only contains items with StatusTodo.Actual
Todojumps to 111 (the view has 115 items in total).Doneappear in theTodocolumn. They also stay in theDonecolumn (71).Evidence
The request sent by the page is correctly scoped to the column:
The response has
totalCount.value = 111(not approximate). On the returned page, 5 of 20 nodes are closed itemswith the Status option id of
Done; the rest are openTodoitems.Same request, only
qchanged (first page, noafter):qclosed:>@today-7d OR no:closed(closed:>@today-7d OR no:closed)no:closed111 = 40 (Todo) + 71 (Done, all closed within the last 7 days). The 4 open items in
In Revieware not part of it.Likely cause
The column condition (
Status = Todo) seems to be appended to the view filter without grouping it. The query is thenevaluated as
closed:>@today-7d OR (no:closed AND Status:Todo), which matches every item closed in the last 7 daysregardless of its Status, plus the open Todo items.
Top-level
ORin Projects view filters is only supported since advanced search became generally available(2026-07-16 changelog), so this may be an edge case of that feature that has not been reported yet. I did not
check when the problem first appeared in this project.
Workaround
Wrap the view filter in parentheses:
(closed:>@today-7d OR no:closed). After saving it, the count ofTodostays at 40 when scrolling.
Notes
Done, only the board rendering is wrong.Guidelines
All reactions