homeblogjira ticket search google chrome omnibox

JIRA ticket search in Google Chrome Omnibox

Did you know that you can add your local JIRA instance as a search engine? I was looking for an easier way to open JIRA tickets, because it was just too cumbersome. I used to either open the JIRA home page and type the ticket into the search box, or edit a URL in my browser history to match the ticket number I was searching for.

With the instructions below, you will be able to type jira modules-3333 into the Omnibox, and it will take you directly to the ticket.

What's the Omnibox, you ask? It's the bar at the top of the browser page that displays the URL where you are at this moment. In Chrome, it's also a place where you can set all kinds of search options. (For more options than I go into here, see this MakeUseOf article, 11 Quick Tricks to Become a Chrome Omnibox Power User.)

In Google Chrome

(other browsers will differ)

  • Click Settings.
  • Under the Search section, click Manage search engines…
  • Scroll all the way to the bottom where the empty text boxes appear.
  • In Add a new search engine, type JIRA.
  • In Keyword, type jira.
    • (Keyword is case sensitive, so remember what you put here. Better yet, stick to lowercase when creating your search engine keywords.)
  • In URL with %s in place of query add https://tickets.puppetlabs.com/secure/QuickSearch.jspa?searchString=%s (You can use this URL to search public Puppet JIRA tickets.)
  • Click Done.

Start searching

Start typing jira modules-3399 (or a ticket relevant to your JIRA instance) into the Omnibox, and it should take you directly to the ticket.

JIRA Search.gif

Some quirks I’ve noticed:

  • Keyword is case sensitive. If your keyword is jira, then using Jira or JIRA will not work.
  • You can’t cut and paste the query into the Omnibox, as it does not trigger the search engine. The keyword has to be typed in manually for it to work. Remember to put in a space after you type jira to trigger the query.

Craig Gomes is an engineering manager at Puppet.

Learn more

UPDATE FROM THE AUTHOR: I've received some great feedback on the blog post, thanks! One update, we've changed the URL for the query so that the search is a little more flexible. Prior to the change, if you entered anything other than a ticket number, you would likely encounter a 404 error when querying against the Puppet JIRA instance. With the updated URL — https://tickets.puppetlabs.com/secure/QuickSearch.jspa?searchString=%s — JIRA will perform a simple text search when you enter text for your search.

To clarify: with the old URL, if you typed in jira modules on the Puppet JIRA instance, you'd get a 404 error. The URL we've changed to fixes that. Try it out and see!