Hey everyone, I need some help setting up JIRA Quick Search in Chrome’s Omnibox. I know you can add a custom search for JIRA IDs, but that’s not what I’m after.
I want to be able to use the same kind of search that JIRA’s Quick Search feature offers, right from the Omnibox. The cool thing about Quick Search is it can find issues even with partial matches.
For example, if I have an issue CLS-77 and it’s the only one with -77 in its ID, typing ‘77’ in Quick Search would take me straight to that issue. But the regular Chrome Omnibox search for JIRA doesn’t do this.
Anyone know how to make this work? It would save me a ton of time not having to go to the JIRA site first. Thanks in advance for any tips!
As someone who’s been using JIRA extensively for years, I’ve found that integrating its search functionality into Chrome’s Omnibox can be a bit tricky. While lucasg’s suggestion is a good start, I’ve discovered a more robust solution that might work better for you.
I developed a custom Chrome extension that hooks into JIRA’s API. It allows for real-time searching directly from the Omnibox, mimicking JIRA’s Quick Search functionality almost perfectly. The extension uses fuzzy matching algorithms to find partial matches, so typing ‘77’ would indeed bring up CLS-77 if it’s the only match.
The setup process is a bit involved, requiring some basic coding knowledge and familiarity with Chrome’s extension architecture. However, once it’s up and running, it’s a massive time-saver. You can configure it to work with multiple JIRA instances too, which is great if you’re juggling different projects.
If you’re interested, I could share more details about the implementation. It’s not a plug-and-play solution, but for power users, it’s worth the initial setup time.
have u tried browser extensions? there’s one called “JIRA Search for Chrome” that might do what u want. it adds a search bar to chrome specifically for JIRA searches. not sure if it does partial matches, but worth checking out. could save u some coding time if it works!
I’ve actually tackled this issue before, and while it’s not a perfect solution, I found a workaround that might help. You can use a custom search engine in Chrome with a wildcard parameter. Set up a new search engine in Chrome’s settings with a keyword (like ‘j’) and use this URL: ‘https://your-jira-instance.com/issues/?jql=key%20~%20"*%25s*"’
This allows you to type ‘j 77’ in the Omnibox, and it’ll search for any issue key containing ‘77’. It’s not exactly like JIRA’s Quick Search, but it comes close. The downside is it opens the search results page instead of going directly to the issue, but it’s still faster than navigating to JIRA first. Hope this helps!