[MaanuAir]

I deal quite a lot with JIRA at my job, as this is a corporate tool.

Often, I get questions about the content of these JIRA issues, by issue key: either orally ("hey, what about PRJ-12345 ?"), or in plain text format in email, i.e. "PRJ-12345" _without_ the hyperlink of course. That could result in going to a https://jira.domain.tld/browse/PRJ-12345, or even https://anotherjira.domain.tld/browse/QSK-54321 (yes we have two, separated, instances running).

Like dozens of time a day.

As the JIRA UI does not make it fast enough for me to lookup for such issues so often (and having two different URLs do not help), I wrote a little Hammerspoon script that listen to a keyboard shortcut key.

When I press it:

- if a JIRA issue key is currently highlighted on screen: it just points my browser to it - if no, an interactive auto-suggester appears and I can type in the issue key, so that I can browse to it immediately as well.

Only a very small automation, but I literally save several precious minutes per day. Mentioning here since the idea might be helpful for others...

[bberenberg]

Your method will be faster, but fyi, you can also put the issue key in the search and it will go directly to the issue. We typically configure search shortcuts in the browser so if you type jABC-123 it will auto expand the j to https://somejira.tld/browse/ABC-123

[TheRealWatson]

That's what I do too but I liked the idea of highlighting and hitting a shortcut, from anywhere. I also configured Sourcetree to match Jira IDs and hyperlink them.

[xemdetia]

I do this by using the JIRA search integration with a prefix, and I have one prefix per relevant JIRA instance I have to talk to. 'j PRJ-12345' is what goes in the search bar and I zip right there.