Sentry: Keyboard shortcuts

[madssj]

Hi.

I think it would be useful to have keyboard shortcuts for navigating sentry, making events as closed and such. Preferably it would be based on gmail's shortcuts.

If there are no plans for keyboard shortcuts, and if the community and you are open for it, I'd be happy to submit a patch.

Mads

[dcramer]

I think keyboard shortcuts could be super helpful. Would love to hear what you have in mind (for the the actions of them).

On Friday, February 1, 2013 at 5:59 AM, Mads Sülau Jørgensen wrote:

Hi.
I think it would be useful to have keyboard shortcuts for navigating sentry, making events as closed and such. Preferably it would be based on gmail's shortcuts.
If there are no plans for keyboard shortcuts, and if the community and you are open for it, I'd be happy to submit a patch.
Mads

—
Reply to this email directly or view it on GitHub (https://github.com/getsentry/sentry/issues/756).

[madssj]

The think that was bugging me was not being able to navigate in the feed. I'd want to add:

j: one entry down
k: one entry up
r: toggle resolved
s: toggle bookmark
enter: go into entry

To the feed list, and perhaps also r and s inside a group.

To take it a step further, one could add a shortcut hook for plugins, so for example, I could make a plugin for an issue tracker and have a b forward the bug to it. That might be another issue though, and it might be possible now as well.

[madssj]

For others, I can recommend vimporator for Firefox or vimium for Chrome until such a time where sentry gets keyboard shortcuts.

[iloveitaly]

:+1:

[mattrobenolt]

I might poke at this since it's a thing I want as well. No guarantees.

[rodneyrehm]

Maybe we can take a cue from github here. Press ? on the project, a file and this issue to see a list of the available commands on the indivudal pages.

[mattrobenolt]

Well, step 1 is adding them in at all. Step 2 is visibility. :)

[raiderrobert]

@mattrobenolt hey, any movement on this perchance?

[mattrobenolt]

Nothing yet. There hasn't really been any demand here.

[iloveitaly]

This would be super helpful—one of the biggest productivity killers in Sentry :/

[VladaPetrovic]

👍 for the shortcuts

[xarg]

A big :+1: here as well.

I would just suggest using the Gmail style shortcuts. j/k,x: select an item, o/enter: open the item, etc...

[sercanov]

Navigating to older events would be great to have

[porn]

(from Jira), in the issue detail:
a: assign issue
i: assign to myself
m: add comment
s: share issue
then it would also make sense to: ignore, resolve, bookmark, delete

[untitaker]

You can hit Ctrl-K in sentry to jump to a specific setting, team or project.

[schteff]

In Chrome that (Ctrl-K) just opens Google Search in the address bar (for me).

[untitaker]

@schteff well it's cmd-k on mac for me but neither ctrl-k nor cmd-k open the addressbar in chrome for me on any website. What OS is this?

[schteff]

Windows 10. See here https://support.google.com/chrome/answer/157179?hl=en-GB under "Windows and Linux" and "Address bar shortcuts".

[untitaker]

Can you click once anywhere on the website before hitting the shortcut? I used to have some sort of focus problem with Slack and Firefox.

[schteff]

Nope, doesn't matter. Even if I select text in Sentry the shortcut only opens Google search.

I have tried all combinations of shift, alt and ctrl (+k).

The same in Firefox, where i noticed shift+ctrl+k opens the browser console.

[schteff]

Wait, you mention Slack. Are you talking about Sentry or Slack?

[untitaker]

I'm mentioning Slack because it also reacts to cmd-k while running in the browser. I wonder whether one works for you while the other doesn't.

[schteff]

Ah, yes, Slack seems to take over the keyboard shortcut. In Slack in Chrome Ctrl+k opens inte internal Slack search.

But not in Sentry.

[billyvg]

@schteff try control-shift-p

[schteff]

@billyvg that opens the print dialog in Chrome and Private Window in Firefox.

[fruitl00p]

This has been bugging me for a while too.. I thought about creating a PR for it using the mousetrap (https://craig.is/killing/mice) with per view possibly different keyboard mapping:
app.jsx:

const keyboardMap = {
'?': () => { console.log('Opens the keyboard mapping modal with an overview and should be available across all views'); },
'c p': () => { console.log('The c followed by p would go to the create project screen (/organizations/[organization]/projects/new/)'); },
'g p': () => { console.log('Go to the project overview (/organizations/[organization]/projects/)'); },
'g i': () => { console.log('Go to the issues overview (/organizations/[organization]/issues/)'); },
'g d': () => { console.log('Go the discover overview (/organizations/[organization]/discover/results/)'); },
'g r': () => { console.log('Go the releases overview (/organizations/[organization]/releases/)'); },
'g u': () => { console.log('Go the user-feedback overview (/organizations/[organization]/user-feedback/)'); },
'g a': () => { console.log('Go the activity overview (/organizations/[organization]/activity/)'); },
'g g': () => { console.log('Go the stats (g as in graphs, as "s" was taken by settings) (/organizations/[organization]/stats/)'); },
'g s': () => { console.log('Go the organization settings (/settings/[organization]/)'); },
'/': () => { console.log('In places where applicable this would open the project dropdown selector'); }
};

issueList/overview.tsx:

const keyboardMap = {
'n': () => { console.log('Next issue'); },
'j': () => { console.log('Next issue (as used i.e. in gmail)'); },
'p': () => { console.log('Previous issue'); },
'k': () => { console.log('Previous issue (as used i.e. in gmail)'); },
'm': () => { console.log('If 2+ issues are selected this would open the merge dialog'); },
'i': () => { console.log('If 1+ issue is selected: ignore the issue(s)'); },
'i f': () => { console.log('If 1+ issue is selected:open the ignore "for" dropdown'); },
'i a': () => { console.log('If 1+ issue is selected:open the ignore "again" dropdown'); },
'i u': () => { console.log('If 1+ issue is selected:open the ignore "until" dropdown'); },

};

GroupDetails.jsx:

const keyboardMap = {
'a': () => { console.log('Opens the resolve dropdown'); },
'a a': () => { console.log('Assign to "me" directly'); },
'ctrl+d': () => { console.log('bookbmark the issue'); },
's': () => { console.log('open the share dropdown'); },
'ctrl+shift+d': () => { console.log('open the delete issue modal'); },
'i': () => { console.log('ignore the issue'); },
'i f': () => { console.log('open the ignore "for" dropdown'); },
'i a': () => { console.log('open the ignore "again" dropdown'); },
'i u': () => { console.log('open the ignore "until" dropdown'); },
'r': () => { console.log('show the resolve dropdown'); },
'r n': () => { console.log('Resolve in next release'); },
'r c': () => { console.log('Resolve in current release'); },
};

There are probably a few more places where a few shortcuts might have a big win, but these seemed the most used to me.

I've looked into a PR and trying to make sense of it all but i got stuck in the actual integration of it.
If anyone else would be willing to pick this up, this would increase productivity alot (imho)

[fruitl00p]

@mattrobenolt still no movement on the keyboard shortcuts?