Action-level shortcuts
Each entry undermetadata.actions[].properties accepts two shortcut keys:
onlyEnabledIfNoOpenExceptions, a pending event subscription, or a locked task) the key does nothing, exactly like a click on the greyed-out button.
Default Save / Cancel shortcuts
The Save and Cancel buttons are not actions, so they take their shortcuts from the template’s own properties (metadata.properties):
hideDefaultSaveButton: true (or hideDefaultCancelButton: true) suppresses the button and its shortcut. The Save shortcut also honours the button’s dirty/locked state: it does nothing when there is nothing to save or the task is locked.
Key syntax
Keys use the same format across task actions and data forms. Combine a key with modifiers using+:
- Modifiers:
control,meta(⌘),alt,shift. The aliasesctrl,cmd,command, andoptionare normalized for you. - Examples:
"a","control+enter","meta+s","meta+shift+s","escape".
The keyboard-shortcuts help dialog
Every bound shortcut carries the button’s label as its description and shows up in the global keyboard-shortcuts help dialog, opened with ⌘ + / (or Ctrl + /). Task-action shortcuts appear there under Actions, listed alongside the shortcuts declared by the data form the reviewer is working in, so a reviewer can always discover what keys are live for the task in front of them.Shortcuts are scoped per task: they register when the task opens and are cleared automatically when it closes or the toolbar unmounts. Opening a different task re-registers only that task’s shortcuts, so keys never bleed across tasks.
Related reading
- Task template patterns — the rest of the action toolbar
- Gating actions on exceptions — disable an action (and its shortcut) until the data is clean
