Major When using folders (plugin), the search returns two results for a unique job: one with the job name and one with the folder plus the job name.
The second one works fine, not the first one.
When the searched phrase exactly matches a job name, you are redirected to that job instead of getting a list of results. As a consequence, searching for a job contained in a folder by its exact name will lead to a 404 page.
For instance, in the attached screenshot, searching for "addons_nuxeo-drive-server-7.10" which is contained in the "7.10" folder:
- hitting enter lead to 404
- waiting for the suggested results returns an unusable "addons_nuxeo-drive-server-7.10" and a working "7.10 addons_nuxeo-drive-server-7.10".
Note also that the both results work fine if the current page is the containing folder. From https://qa.nuxeo.org/jenkins/job/7.10/ , both the "relative path" "addons_nuxeo-drive-server-7.10" and the "folder relative or absolute 
path" "7.10 addons_nuxeo-drive-server-7.10" will work.
It is not clear if "7.10 addons_nuxeo-drive-server-7.10" is an absolute or relative, full or partial path... What happens with a job contained in sub folders...?
- duplicates
-
JENKINS-35459 Duplicated elements with incorrect URL when using the search on DashBoard View
-
- Resolved
-
- is related to
-
-
- Resolved
-
- links to
[JENKINS-35158] search box provides 404 and duplicates results for jobs in folders
I confirm the functionality is still unsupported. Moreover, the extension engine for Search Factories is not designed well for such nested searches
Julien Carsique
added a comment - Depending on how much time is required to properly fix that feature, it could be relevant to first add a post filtering as a workaround: displaying invalid URLs is confusing and, moreover, the redirect to 404 in case of exact match is a bigger issue: users complain that the job is missing or that the URL is broken...
Julien Carsique
added a comment - Depending on how much time is required to properly fix that feature, it could be relevant to first add a post filtering as a workaround: displaying invalid URLs is confusing and, moreover, the redirect to 404 in case of exact match is a bigger issue: users complain that the job is missing or that the URL is broken... I can re-produce sometimes the issue on your instance, but not on a fresh instance. Without a re-producible scenario on fresh instance I find hard to understand why the issue is happening and to fix it.
As I said, on a fresh instance this issue is not re-producible using the same core version you are using and with latest Jenkins bits.
Also seeing this on Jenkins 2.46.3 with CloudBees Folders 6.0.3. Issue is exactly as described; jobs in folders have two results, and the first one returns a 404, but the second is qualified with the folder before the name and works.
mcrooney
added a comment - - edited Also seeing this on Jenkins 2.46.3 with CloudBees Folders 6.0.3. Issue is exactly as described; jobs in folders have two results, and the first one returns a 404, but the second is qualified with the folder before the name and works. 
Davide Bolognini
added a comment - Same problem with 2.73.1. What kind of view is the search run in? IIRC the search functionality depends on the current view.
The fix has been released in Jenkins 2.86, so it will be available in the next LTS release
Philip Johnson
added a comment - I reopened this issue as it was reproducible in v2.150.3 with Folders plugin 6.8, but having updated to v2.164.1, the issue is resolved, so this can be marked as resolved again. Thanks.
Philip Johnson
added a comment - I reopened this issue as it was reproducible in v2.150.3 with Folders plugin 6.8, but having updated to v2.164.1, the issue is resolved, so this can be marked as resolved again. Thanks. Philip Johnson
added a comment - I reopened this issue as it was reproducible in v2.150.3 with Folders plugin 6.8, but having updated to v2.164.1, the issue is resolved, so marking it as resolved again.
Philip Johnson
added a comment - I reopened this issue as it was reproducible in v2.150.3 with Folders plugin 6.8, but having updated to v2.164.1, the issue is resolved, so marking it as resolved again. I am able to reproduce this issue on Jenkins v2.174/Folders v6.8, however, I have two installations with these versions and only one has the issue. Other plugin versions are different and this may be a factor.
André Carmo
added a comment - This issue also happens to me in 2.249.2. 
Luis Ehlen
added a comment - Same for 2.263.2 
Allan BURDAJEWICZ
added a comment - Still happens as of 2.319.3 apparently 
Mario Hochreiter
added a comment - Same issue here. Jenkins version 2.332.1. Folders plugin: 6.708.ve61636eb_65a_5
Mario Hochreiter
added a comment - Same issue here. Jenkins version 2.332.1. Folders plugin: 6.708.ve61636eb_65a_5 This is very annoying!
Jenkins 2.340 and Folder 6.714.v79e858ef76a_2
What version of Jenkins is this?