KEYJUMP

Docs

Setup

  1. Open the Keyjump settings page (click the icon in the toolbar).
  2. Paste the URL of a Jira site you use, for example https://acme.atlassian.net.
  3. Add one row per project prefix, pointing each at the site that owns it.
  4. Optionally set a fallback site for prefixes not in the table.
  5. Save. Type j, space, and a key to test.

The two modes

Keyword mode. Type j, space, then the key. Works out of the box with zero site access. The suggestion row shows the destination before you press Enter. Alt+Enter opens the ticket in a new tab.

Address bar mode. Type the key on its own, like acme-42. Off by default. Turning it on asks Chrome for permission to see search queries. Only exact matches on configured prefixes are redirected, everything else searches as normal.

Troubleshooting

The key does not resolve

Almost always one of two things, and both are easy to miss by eye.

A trailing space on the prefix. ACME and ACME look identical in the settings table and are not the same. Click into the field, press End, and check the cursor sits against the last letter.

Or /browse left on the end of the site URL. Keyjump adds that part itself, so https://acme.atlassian.net/browse becomes https://acme.atlassian.net/browse/browse/ACME-42. The site should stop at the hostname.

The address bar still searches instead of jumping

Bare key mode is off until you switch it on, and it needs a permission you have to approve. Open settings and check the address bar option is ticked. If ticking it did nothing, the Chrome prompt was probably dismissed; untick and tick it again to bring the prompt back.

It also only fires on an exact match for a prefix you configured. Anything else is left alone deliberately, so your ordinary searches keep working.

The j keyword does not trigger

Type j then press space or Tab before the key. Without that, Chrome treats the whole thing as a search.

If another extension has claimed j, whichever was installed first wins. Check chrome://extensions and remove the other one, or disable it to test.

Settings did not appear on my other machine

Settings ride on Chrome sync, so both machines need to be signed into the same Chrome profile with sync switched on, and extension settings included in what syncs. Managed work profiles often have this turned off by policy, and nothing in Keyjump can override that.

Sync is also not instant. If everything looks right, give it a few minutes.

Uninstalling

Right-click the toolbar icon and choose Remove from Chrome, or use chrome://extensions.

Removing it deletes your routing table and preferences along with it. Any permission you granted for bare key mode goes at the same time. Nothing is left behind on your machine and there was never anything held anywhere else, so there is no account to close and nothing to request deletion of.

If you want your routing table back later, copy it somewhere before you uninstall. There is no export yet.

FAQ

Does it work with Jira Server or Data Center?

Yes. Any base URL works, as long as tickets live at /browse/KEY-123.

Two clients use the same prefix. What happens?

A prefix maps to exactly one site. Rename one entry, for example route APP to one site and use the fallback for the other.

Is a lowercase key fine?

Yes. orbit-118 and ORBIT-118 are the same key.

What does Keyjump send over the network?

Nothing. It builds a URL locally and opens it. See the privacy page.

Can I sync settings between machines?

Settings live in your browser profile, so Chrome sync carries them between your own devices if you have it on.