WISH: Option to set default search parameters for 'Issues' and 'Pull requests' (or custom 'Tabs') #3932

Open
opened 2025-11-02 05:31:01 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @HenrikBengtsson on GitHub (Sep 10, 2019).

  • Gitea version (or commit ref):
  • Git version: 1.9.3
  • Operating system: Linux, CentOS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When viewing a repository's 'Issues' page, the default URL is of kind:

Although, no query parameters are used, this defaults to listing/searching open issues.

My proposal is to make the default search query to be configurable per repository. For instance, for some repositories we might want to list all open issues with a certain set of labels, milestones, and so on, set, e.g.

This would provide a poor man's solution to displaying only issues of certain importance, e.g. those labelled say 'High priority', 'Pinned', ...

The downside would be the "surprise factor" that it could be confusing when 'Issue' works differently across repositories. An alternative would be to add support for per-repository customized 'Tabs' that repos owners can inject in the 'Code', 'Issues', 'Pull requests', 'Releases', 'Wiki', 'Activity' suite, e.g.

  • 'Code', 'Issues', 'High Priority Issues', 'Pull requests', 'Releases', 'Wiki', 'Activity'

This is related to feature requests on Pinned Issues, cf. Issue #2616.

Originally created by @HenrikBengtsson on GitHub (Sep 10, 2019). - Gitea version (or commit ref): - Git version: 1.9.3 - Operating system: Linux, CentOS - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description When viewing a repository's 'Issues' page, the default URL is of kind: * https://gitea.com/gitea/tea/issues Although, no query parameters are used, this defaults to listing/searching open issues. My proposal is to make the default search query to be configurable per repository. For instance, for some repositories we might want to list all open issues with a certain set of labels, milestones, and so on, set, e.g. * https://gitea.com/gitea/tea/issues?q=&type=all&state=open&labels=435 This would provide a poor man's solution to displaying only issues of certain importance, e.g. those labelled say 'High priority', 'Pinned', ... The downside would be the "surprise factor" that it could be confusing when 'Issue' works differently across repositories. **An alternative** would be to add support for per-repository customized 'Tabs' that repos owners can inject in the 'Code', 'Issues', 'Pull requests', 'Releases', 'Wiki', 'Activity' suite, e.g. * 'Code', 'Issues', '**High Priority Issues**', 'Pull requests', 'Releases', 'Wiki', 'Activity' ## Related to This is related to feature requests on Pinned Issues, cf. Issue #2616.
GiteaMirror added the type/proposaltopic/ui labels 2025-11-02 05:31:01 -06:00
Author
Owner

@Harfusha commented on GitHub (Oct 29, 2024):

I would love this feature

@Harfusha commented on GitHub (Oct 29, 2024): I would love this feature
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3932