Bug 364140

Summary:	Product search without wildcards doesn't work as expected
Product:	[Websites] bugs.kde.org	Reporter:	Stefan Monov <logixoul>
Component:	general	Assignee:	KDE sysadmins <sysadmin>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	ddascalescu+kde, nate, sheedy
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Other
URL:	https://bugs.kde.org/enter_bug.cgi?format=guided
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Search only works for prefixes

Description Stefan Monov 2016-06-09 11:35:14 UTC

Pretty much every search box I've ever used (e.g. Google web search) treats the search terms as "must be *contained* in the text to match". For example, "trainer" without the quotes, in description-search box, should match "Pronunciation trainer", but doesn't. Adding *'s like in "*trainer*" works, though.
Due to this problem at first I thought the product I was looking for was missing and was about to write to a mailing list asking for directions. Only after I thought of trying ctrl+F did I find the product and figured that wildcards were what I was missing at first.

Reproducible: Always

Steps to Reproduce:
1. Go to https://bugs.kde.org/enter_bug.cgi?format=guided
2. Write "trainer" without the quotes, in the right search box. Or write "windows" without the quotes, in the left search box.
3. Press Enter.

Comment 1 Frédéric Sheedy 2016-06-10 00:46:31 UTC

Confirmed, this is a nice to have, "*" is required and description how to search is on the page.

Comment 2 Dan Dascalescu 2016-09-04 02:15:11 UTC

Created attachment 100917 [details]
Search only works for prefixes

This isn't a "nice to have" nowadays. It's a key feature and its lack keeps hurting users.

I wasted a bunch of time trying to file a bug against plasmashell was was made fun of because I couldn't find the product. See bug 368176 and
https://forum.kde.org/viewtopic.php?f=289&t=135101&p=363323#p363306

Comment 3 Nate Graham 2022-09-02 19:23:19 UTC

Regrettably we no longer have a search/filter field on that page (see 455605 which proposes bringing it back), so I'm afraid this bug report is now obsolete.