Elyra
Elyra The coding agent e The native code editor Elyra Grove Native local development environment Askr The real server for Laravel & PHP Elyra Framework Rust + Svelte 5 framework for desktop apps Elyra Conductor Local project conductor Elyra SQL Server MySQL-compatible SQL server in Rust Elyra Félagi Agents as teammates on one board Elyra SQL Client Native desktop SQL workbench Elyra SQL Anywhere Replication-ready SQL engine Elyra Sjá SEO & GEO workspace for macOS Elyra DataGrid Server-driven data grid for Laravel
Start here
Concepts
Release notes
What's new
Elyra

Keyboard

Press ? anywhere to see the list. That is the only one worth memorising, because it tells you the rest.


Where you are

Key Does
c New issue — from any page, not only the board
/ Search everything
⌘K / Ctrl-K Search everything
? The list
esc Close whatever is open

Going somewhere

Press g, then a letter. A g pressed by accident is forgotten after a moment, so the next ordinary keystroke does not turn into a journey.

Keys Goes to
g d Dashboard
g i Issues
g e Epics
g p Projects
g c Cycles
g b Inbox
g t Timesheets
g k Knowledge
g r Reports

Two keys rather than one, on purpose. Single letters are spent on what you do to the thing in front of you; going somewhere else is a deliberate pair — and it leaves the whole alphabet free for the first kind.


Never while you are writing

Nothing here fires inside a field, a comment, a description or a search box. In those, the keys are just letters.

This is the rule the rest depends on. A shortcut that goes off inside a comment is worse than no shortcut at all: c in the middle of a sentence opening a panel is how somebody stops trusting an application, and afterwards they use the mouse for everything.

The same applies while a dialog is open — it owns the keyboard until you close it.


What is not here yet

  • No j/k to move between rows. Moving a highlight through a list needs somewhere for the highlight to be, and a half-built version of that is more confusing than none.
  • No e to edit, no a to assign. Shortcuts that act on "the current issue" need a current issue, which is the same missing idea.

Both wait for row selection to exist. Doing them badly would teach people the keyboard is unreliable here, which is expensive to undo.


Related

  • Search — what ⌘K looks through, and what it will not find