View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0013979||mantisbt||feature||public||2012-02-28 18:31||2019-03-19 16:17|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0013979: Top nav search functionality, e.g. top "Jump" bar could accept search terms for quicker search navigation.|
I came to report this issue because I found a convenience issue with the need to click through to "view issues" before you can search for a term. It would be much more convenient to have direct access to a keyword search in the top header at all times than to have to click through a certain link to get access to it.
|Steps To Reproduce|
Try to search for an issue by keyword.
If you have a keyword, say "Particle", and you want to find an issue with that keyword, you will generally have to A: be familiar enough with the interface that you know that searching is available only within the "View Issues" link, and B: click through the "view issues" link, load that new page, and then find the search box part way down that page and then do the search before you get your results.
Now, there's already a "search" type box in the header that currently only accepts integers and just gives an error on anything else.
With a if((int) $term = $term) type check and branching, it could act as a search box, using any integers as a check for issue numbers and everything else as a keyword search by passing the term through to the filter search results page here:
Obviously there are a variety of other ways to implement this as well.
|Tags||No tags attached.|
Maybe this plugin http://git.mantisforge.org/w/MantisCmd.git can do what you need
....a command line interface? ...does it also add to the web ui or something?
It's just a text field that is displayed on MantisBT header, allowing you to enter some commands including "s" for search.
2018: similar request in forum.
Could you replace the the field "entry #" on dashboard page by a full text search, please?
+1 from me. If the 'jump' field could do a keyword search if the string did not match an exact issue number, that'd be nice.
|2012-02-28 18:31||tchalvakspam||New Issue|
|2012-02-29 03:45||dregad||Note Added: 0031351|
|2012-02-29 10:54||tchalvakspam||Note Added: 0031354|
|2012-03-01 03:26||dregad||Note Added: 0031356|
|2018-04-12 13:53||Starbuck||Note Added: 0059543|
|2018-06-01 15:53||IchSelbst||Note Added: 0060005|
|2019-03-19 16:17||rogueresearch||Note Added: 0061717|