You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When on the issue list that displays all issues open in your repositories, the pagination always uses the absolute issue count instead of only the issues currently visible due to filtering.
Did a bit of diging and found the source of it: the problem is that the route only fills in the pagination with the total open/close count, but dosn't respect any selected repos:
Fixes#19791 by adding an check if filtering after any repo; if yes, simply set the total count for the pageing to the sum of the issue count for each selected repo by utilize `issueCountByRepo`.
Fix#19791
…9801)
Fixesgo-gitea#19791 by adding an check if filtering after any repo; if yes, simply set the total count for the pageing to the sum of the issue count for each selected repo by utilize `issueCountByRepo`.
Fixgo-gitea#19791
Description
When on the issue list that displays all issues open in your repositories, the pagination always uses the absolute issue count instead of only the issues currently visible due to filtering.
Gitea Version
1.16.8
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Screenshot from try.gitea.io:
Git Version
No response
Operating System
No response
How are you running Gitea?
binary installation from https://docs.gitea.io/en-us/install-from-binary/; also try.gitea.io
Database
MySQL
The text was updated successfully, but these errors were encountered: