-
-
-
@servicedesk OD-3099 created, please close this
-
-
Previous Value Current Value Open
Closed
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
@servicedesk OD-3099 created, please close this
| Previous Value | Current Value |
|---|---|
Open | Closed |
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Problem
Project navigation and common creation actions currently require pointer use or repeated menu navigation. Advanced keyboard users need fast, memorable sequences that work consistently across project pages without conflicting with text entry.
Proposed behavior
Extend the existing command palette with a dedicated shortcut mode.
ooutside an editable context to open the palette filtered to project navigation commands.noutside an editable context to open the palette filtered to creation commands that are currently available to the user.kor the.command-palettebutton keeps its existing behavior. It displays shortcut sequences for discoverability, but typing those sequences there does not activate them.Navigation sequences
ooopouogowofocobotomodoiokoeoscosposiosbCreation sequences
At minimum, support the requested eligible actions:
ninpntnbOnly show and activate a creation command when the corresponding project feature is available and the current user has permission. Unsupported sequences must not trigger an action.
Editable-context safety
Do not start or execute shortcut sequences while focus is in an editable or text-entry context, including text inputs, textareas, selectors, and content-editable/rich-editor components. After the user exits the editable context, shortcuts work normally.
Acceptance criteria
oandnopen visibly filtered shortcut modes with continuation keys displayed.oorngroup filter.