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

Unable to search issues for part of a word. #2967

Open
2 of 7 tasks
Tracked by #4
sgtwilko opened this issue Nov 24, 2017 · 13 comments
Open
2 of 7 tasks
Tracked by #4

Unable to search issues for part of a word. #2967

sgtwilko opened this issue Nov 24, 2017 · 13 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality

Comments

@sgtwilko
Copy link

  • Gitea version (or commit ref): 1.2.3
  • Git version: 2.15.0
  • Operating system: Windows
  • 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

The Issue search does not find an issue when searching for part of a word within the issue name/description.

We discovered this as we had created an issue for each file we needed to deal with.
Our filenames have a specification that indicates where and what the purpose is of the file.
For example:
Customer_SupportTicketRaise

If we search the issues for "SupportTicket" or "Customer" no issues are returned as this would only match a partial string.
I can understand that searching for part of a string could return too many results for most people, but either including those results below the full string match, or having the option to search for a partial string would be better as, at first, we thought the entire search was broken.

Screenshots

Created serveral issues:

image

Searched for "dave" but it failed to find "test_dave":
image

@lunny
Copy link
Member

lunny commented Nov 25, 2017

I think this is a designed feature. And currently it also don't support CJK languages.

@lunny lunny added the type/enhancement An improvement of existing functionality label Dec 4, 2017
@ncantelmo
Copy link

Hey all,

I just upgraded from Gogs yesterday specifically because I saw that issue search had been added to Gitea. I'd like to second this enhancement request, but also request that fuzzy matching be considered as part of it.

When you're adding to a large backlog and you don't remember the exact terms you used (e.g. migrate vs. migration vs. migrations), it can be easy to miss an existing issue and create a duplicate.

@stale
Copy link

stale bot commented Feb 9, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@JVimes
Copy link

JVimes commented Feb 14, 2023

Search for click didn't find clicks for me. Very surprising. This is a moderately large problem for me.

@lunny
Copy link
Member

lunny commented Feb 15, 2023

Since Gitea has 3 engines for issue indexing, I assume we are talking about bleve. #22829 has resolved camelCase problem.

@JVimes
Copy link

JVimes commented Feb 15, 2023

@lunny Does #22829 make query "click" find result "clicks" (with the "s")?

@lunny
Copy link
Member

lunny commented Feb 16, 2023

@lunny Does #22829 make query "click" find result "clicks" (with the "s")?

Not yet. Looks like bleve doesn't support that, we may need to write a customized token filter

@wxiaoguang
Copy link
Contributor

Bleve has some stemers:

That issue mentions that "snowball and porter stemmers" can stem words to their origins.

(Just come across, FYI)

@JVimes
Copy link

JVimes commented Feb 16, 2023

If stemmers can implement partial-word matches that would solve the general case. Otherwise I think they would help a bit.

@jgschis
Copy link

jgschis commented Mar 3, 2023

You can use the ngram analyser to do partial string matching.

So customer_support_ticket

could be ngrammed as

cus
cust
custo
custom
custome
customer
customer_
etc

@Leon-001
Copy link

Or at least a wildcard symbol such as "*" or "%" would be great!

@coolbombom
Copy link

any news regarding this issue. when will it be integrated/fixed?

@hakito
Copy link
Contributor

hakito commented Jun 17, 2024

At least a prefix based search now works (when using an external indexer like meilisearch)

But only for the global issues search and not on the repo level :-(

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/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

9 participants