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

Backoffice search returns irrelevant results because Key is part of the search query #16003

Open
mcl-sz opened this issue Apr 7, 2024 · 1 comment · May be fixed by #16004
Open

Backoffice search returns irrelevant results because Key is part of the search query #16003

mcl-sz opened this issue Apr 7, 2024 · 1 comment · May be fixed by #16004
Labels

Comments

@mcl-sz
Copy link
Contributor

mcl-sz commented Apr 7, 2024

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.2

Bug summary

The backoffice search gives irrelevant results because Key is part of the searches. This is a problem, especially for short searches.
If the key contains the letters of the search query, these are returned as a result.

Specifics

No response

Steps to reproduce

The easiest way to reproduce this is to install Paul Seals Clean Starter Kit.

The starter kit includes an "About" page. Search the backoffice for "ab"

afbeelding

Depending on your installation, you will find multiple result that at first glance have nothing to do with the search query. These results are shown because "ab" appears in the Key field.

Expected result / actual result

It is logical that it can be useful to also be able to search on the Key field, but only if it concerns a complete Key. In the current situation this is also found if a few letters match. This doesn't make sense.

@mcl-sz mcl-sz added the type/bug label Apr 7, 2024
Copy link

github-actions bot commented Apr 7, 2024

Hi there @mcl-sz!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant