Improve searching #6606

Open
opened 2025-11-02 07:01:10 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @DuckDuckWhale on GitHub (Dec 30, 2020).

  • Gitea version (or commit ref): 1.13.1
  • Git version: 2.25.1
  • Operating system: Ubuntu Server 20.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Haven't tried
  • Log gist: N/A

Description

There are a few inconveniences with searching in Gitea. In the issue labels, searching for the second word in the label doesn't work, for example, searching high doesn't show priority: high. In the global issues page searching for issues require you to remember the keywords exactly as they are, or it won't work. For example, if you have an issue called Fix the bugs, and you search for bug, it won't show up. I think this is annoying and unnecessary. Maybe a more relaxed search function would work better, or better yet use a fuzzy search.

Originally created by @DuckDuckWhale on GitHub (Dec 30, 2020). - Gitea version (or commit ref): 1.13.1 - Git version: 2.25.1 - Operating system: Ubuntu Server 20.04 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Haven't tried - Log gist: N/A ## Description There are a few inconveniences with searching in Gitea. In the issue labels, searching for the second word in the label doesn't work, for example, searching `high` doesn't show `priority: high`. In the global issues page searching for issues require you to remember the keywords exactly as they are, or it won't work. For example, if you have an issue called `Fix the bugs`, and you search for `bug`, it won't show up. I think this is annoying and unnecessary. Maybe a more relaxed search function would work better, or better yet use a fuzzy search.
GiteaMirror added the type/proposal label 2025-11-02 07:01:10 -06:00
Author
Owner

@DuckDuckWhale commented on GitHub (Jan 3, 2021):

Also, when adding dependencies and using the search there, it is intuitive to search 123 or #123 for issue number 123, but this doesn't work either.

@DuckDuckWhale commented on GitHub (Jan 3, 2021): Also, when adding dependencies and using the search there, it is intuitive to search `123` or `#123` for issue number 123, but this doesn't work either.
Author
Owner

@tyroneyeh commented on GitHub (May 30, 2022):

Also, when adding dependencies and using the search there, it is intuitive to search 123 or #123 for issue number 123, but this doesn't work either.

You could try this https://github.com/go-gitea/gitea/issues/4109#issuecomment-1140187263

@tyroneyeh commented on GitHub (May 30, 2022): > Also, when adding dependencies and using the search there, it is intuitive to search `123` or `#123` for issue number 123, but this doesn't work either. You could try this https://github.com/go-gitea/gitea/issues/4109#issuecomment-1140187263
Author
Owner

@tyroneyeh commented on GitHub (May 30, 2022):

Blevesearch improve maybe could using the patch c2bf9a3630

  1. Default Search is title field is "and" matches ex: keyword1 keyword2
  2. Can using "tes*" like to regex search
  3. Can using "hello|hi" to or match keywords
  4. "content: keyword" for search content keywords
  5. "comments: keyword" for search comments contents keywords
@tyroneyeh commented on GitHub (May 30, 2022): Blevesearch improve maybe could using the patch https://github.com/tyroneyeh/gitea/commit/c2bf9a36306011ec6f4ad4fac1abd017169c1415 1. Default Search is title field is "and" matches ex: keyword1 keyword2 2. Can using "tes*" like to regex search 3. Can using "hello|hi" to or match keywords 4. "content: keyword" for search content keywords 5. "comments: keyword" for search comments contents keywords
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6606