[JIRA] [core] (JENKINS-19393) global search should not jump to exact result if more than one result is found

Mon, 14 Jul 2014 11:27:06 -0700

Daniel Beck commented on Improvement JENKINS-19393

Probably more of a terminology issue leading to expectations that don't match reality: The "search" in Jenkins seems to be set up to be some kind of "quick navigation" (similar to desktop tools like Quicksilver, LaunchBar, Enso Launcher, …) rather than a plain "search". Supporting indicators:

  1. If an exact match can be found, it navigates to the result
  2. It supports queries like projectname #2 console which have nothing to do with actual keyword search (if there's a build #2, it will have a console output page, so search is pointless)
  3. Searching for inexact 'launcher' type queries like projectname console will fail
  4. If no exact match can be found, the resulting web page is a 404 error page with suggestions (i.e. showing this is definitely not the default operation)

I'm not saying this shouldn't be changed – I've never even used search as "launcher" except to try it – but this should give you an idea that it's not just "get rid of the exact match resolution and done". In fact, I tried it, and the problem is that even the suggested results on the "error page" only link to the search page, assuming their exact match will result in jumping to the referenced item – so the search API needs to be changed to support a list of name/URL pairs instead of just names as currently.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to