Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues belonging to a repository cannot be filtered by "no assignee" #31520

Closed
galip16 opened this issue Jun 28, 2024 · 0 comments · Fixed by #31522
Closed

Issues belonging to a repository cannot be filtered by "no assignee" #31520

galip16 opened this issue Jun 28, 2024 · 0 comments · Fixed by #31522
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Milestone

Comments

@galip16
Copy link

galip16 commented Jun 28, 2024

Description

While attempting to filter issues within a repository, issues cannot be filtered by the "no assignee" criteria. This makes it difficult to locate issues that are not assigned to any specific individual.

Gitea Version

1.22.0

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

MacOS - Chrome

How are you running Gitea?

Using official docker image

Database

None

@kemzeb kemzeb added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jun 28, 2024
GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Jul 23, 2024
@lunny lunny added this to the 1.22.2 milestone Jul 24, 2024
wolfogre pushed a commit that referenced this issue Jul 24, 2024
Backport #31522 by @kemzeb

Quick fix #31520. This issue is related to #31337.

Co-authored-by: Kemal Zebari <60799661+kemzeb@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants