[feature]: keyboard shortcuts missing for some of the most common operations
@vihar is already working on this.
Since May 10, 2026.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Is there an existing issue for this?
- I have searched the existing issues
Summary
I'm extremely excited to be trying out Plane for the first time - it looks really amazing!
I'm coming from Linear and I was really pleased to find that many of the keyboard shortcuts are very similar, because they are really well designed in Linear.
However I was really surprised to find that apparently there are no keyboard shortcuts for many of the most common actions needed on a day-to-day basis.
Here's what I would expect, based on my experience from Linear, GitHub, and many other systems:
| Action | Typical keyboard shortcut (e.g. Linear) |
|---|---|
| Next item in list | J, Down arrow |
| Previous item in list | K, Up arrow |
| Open a peek view of an item | Enter |
| Open item full-screen in a new tab | Control + Enter |
| Toggle item selection | X |
| Select all items | Control + A |
| Filter | F |
| Archive from inbox | E |
| Change field on selected work item in inbox | Same shortcuts as in normal view for a single work item, e.g. S for status, L to label |
| Bulk change field on all selected work items | Same shortcuts as in normal view for a single work item, e.g. S for status, L to label |
| Open a specific work item by id or title | O I (/ search is much less precise because it searches across all entities) |
| Show keyboard shortcuts | ? (it's on Control + / despite #1428 and #5000) |
Why should this be worked on?
These alone would make an enormous difference to the usability of Plane, because they are far faster than doing these operations with the mouse.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.