I want to use JIRA’s Quick Search feature directly from Chrome’s address bar. The regular Chrome search setup with https://mycompany/jira/browse/%s doesn’t work the same way. That URL only opens tickets when you type the exact ticket number. But JIRA’s Quick Search is smarter - it finds tickets even with partial matches. Like if I have ticket ABC-123 and I search for just “123” in JIRA’s search box, it opens ABC-123 automatically. The Chrome address bar method won’t do this with partial numbers. How can I make Chrome’s omnibox work like JIRA’s Quick Search?
Had this exact problem at my last job and found a decent workaround. Skip the browse URL and set up Chrome’s search engine with JIRA’s actual search endpoint instead. Use https://mycompany/jira/secure/QuickSearch.jspa?searchString=%s as your URL pattern. This hits the same backend as JIRA’s quick search box, so you get the smart matching you want. Downside is it dumps you on a search results page instead of going straight to the ticket, but it’s usually one click since smart matching puts the right ticket at the top. Been using this for two years now - saves tons of time vs remembering exact ticket numbers.
theres another approach that worked for me - try the global search endpoint https://mycompany/jira/secure/GlobalSearch.jspa?q=%s. its more forgiving than the browse url and searches issue summaries, not just keys. if you remember part of the ticket title, it’ll find it. slower than direct browse but way more flexible.
Check if your JIRA instance supports REST API queries through the address bar. I’ve got Chrome set up with https://mycompany/jira/rest/api/2/search?jql=key~%s and it works great - uses JIRA’s JQL search for partial matching. Takes some trial and error with the JQL syntax, but it’s way better than the basic browse URL. You might need to tweak the query parameter depending on your JIRA version since some installations use different REST endpoints. The magic is the tilde operator (~) in JQL - it does fuzzy matching on ticket keys. Test it in JIRA’s advanced search first to make sure your instance supports this syntax before setting up the Chrome search engine.