Ability to view all issues assigned to a user at org-level #12069

New Issue

GiteaMirror · 2025-11-02T09:56:44-06:00

GiteaMirror commented

2025-11-02 09:56:44 -06:00

Originally created by @eeyrjmr on GitHub (Nov 22, 2023).

Feature Description

At repository level you are able to filter issues based upon Assignee. It would be extremely useful for team reviews with multiple repositories to perform a similar filtering at org-level across all repositories. Presently only sorting can be done at org-level issue view based upon newest, oldest etc... while repo level can sort AND filter (label, project, author, assignee, type)

http://192.168.0.1/ORG/REPO/issues vs http://192.168.0.1/ORG/issues

Screenshots

No response

Originally created by @eeyrjmr on GitHub (Nov 22, 2023). ### Feature Description At repository level you are able to filter issues based upon Assignee. It would be extremely useful for team reviews with multiple repositories to perform a similar filtering at org-level across all repositories. Presently only sorting can be done at org-level issue view based upon newest, oldest etc... while repo level can sort AND filter (label, project, author, assignee, type) http://192.168.0.1/ORG/REPO/issues vs http://192.168.0.1/ORG/issues ### Screenshots _No response_

GiteaMirror added the type/proposal issue/needs-feedback labels 2025-11-02 09:56:44 -06:00

GiteaMirror closed this issue

2025-11-02 09:56:45 -06:00

GiteaMirror commented

2025-11-02 09:56:46 -06:00

@lng2020 commented on GitHub (Nov 23, 2023):

More background: The issue overview page(http://{host}/org/{org name}/issues) examines the issues related to you at the org level. Its underlying search engine does have some fields like assignee or project, but the routing layer has set those fields automatically, like assignee: currentUser.ID.
I think this page ideally can search with keywords such as assignee: xxx just like GitHub. However, there are other codes that rely on the search engine which are not easy to decouple.

@lng2020 commented on GitHub (Nov 23, 2023): More background: The issue overview page(http://{host}/org/{org name}/issues) examines the issues **related to you** at the org level. Its underlying search engine does have some fields like `assignee` or `project`, but the routing layer has set those fields automatically, like `assignee: currentUser.ID`. I think this page ideally can search with keywords such as `assignee: xxx` just like GitHub. However, there are other codes that rely on the search engine which are not easy to decouple.

GiteaMirror commented

2025-11-02 09:56:46 -06:00

@coolbombom commented on GitHub (Apr 9, 2024):

i really think this a missing feature too. I had to move a users issues to another user. Really annoying i had to got into all repo to move the issues instead of just having the overview off all issues on org level for that user.

@coolbombom commented on GitHub (Apr 9, 2024): i really think this a missing feature too. I had to move a users issues to another user. Really annoying i had to got into all repo to move the issues instead of just having the overview off all issues on org level for that user.

GiteaMirror commented

2025-11-02 09:56:46 -06:00

@wxiaoguang commented on GitHub (Dec 11, 2024):

I think it will be supported by this? Add label/author/assignee filters to the user/org home issue list #32779

@wxiaoguang commented on GitHub (Dec 11, 2024): I think it will be supported by this? Add label/author/assignee filters to the user/org home issue list #32779

GiteaMirror commented

2025-11-02 09:56:46 -06:00

@GiteaBot commented on GitHub (Jan 11, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Jan 11, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12069