Jira Keyboard Shortcuts
Jira's shortcut set is dense and largely modeled on single-letter bindings reminiscent of email clients like Gmail, since its core interaction is scanning a list of issues and acting on whichever one currently has focus. The shortcuts here are scoped to Jira Cloud's modern interface; Jira Server/Data Center installations and older interface versions can have slightly different bindings for some actions, so if a shortcut doesn't respond as described, checking your specific Jira version and edition is worth doing before assuming the shortcut itself is wrong. Engineering managers running daily standups against a sprint board, and individual developers triaging their own assigned backlog before starting a coding session, both rely on largely the same handful of shortcuts, which is part of why learning even a small subset — create, assign, comment, and the J/K navigation pair — pays off regardless of whether your primary relationship with Jira is planning work or actually doing it. Linking related issues and jumping straight to the backlog both matter once a project grows past a handful of tickets, since tracking dependencies between stories and separating backlog grooming from active-sprint execution are core to how most agile teams actually use Jira day to day, beyond just creating and closing individual tickets one at a time.
Issue Actions
| Action | Windows | Mac | Description |
|---|---|---|---|
| Create new issue | C | C | Opens the Create Issue dialog from anywhere in Jira, prefilled with sensible defaults based on your current project context if applicable. |
| Assign focused issue | I | I | Opens the assignee picker for the currently selected or open issue, letting you reassign without navigating into a full edit form. |
| Add comment to focused issue | M | M | Jumps the cursor directly into the comment field of the open issue, skipping the need to scroll down and click into it manually. |
| Edit focused issue | E | E | Opens the full edit form for the currently open issue, letting you modify any field rather than just the quick-access ones available via other single-letter shortcuts. |
| Log work on focused issue | L | L | Opens the work log dialog to record time spent on the issue, relevant for teams tracking effort against estimates. |
| Watch/unwatch focused issue | G then W (varies; sometimes a dedicated watch icon click) | G then W | Toggles whether you receive notifications for changes to the issue, without needing to open the issue's watcher list manually. |
| Move focused issue to next workflow status | Period (.) then select transition | — | Opens a quick-transition menu for moving the current issue through its workflow (like from 'In Progress' to 'Done'), a faster alternative to opening the issue and clicking the status dropdown directly. |
| Inline quick-edit a field | Click field then Tab, or dedicated single-letter for common fields | — | Many issue fields support inline editing directly within the detail view without opening a separate edit form, distinct from the E shortcut's full edit mode which opens every field at once rather than just the one you clicked into. |
| Link focused issue to another issue | Ctrl+Shift+L (varies by instance) | Cmd+Shift+L | Opens the issue linking dialog to relate the current issue to another (blocks, is blocked by, relates to), useful for capturing dependencies between tickets that a flat backlog list wouldn't otherwise show. |
Navigation
| Action | Windows | Mac | Description |
|---|---|---|---|
| Open Jira search | / | / | Focuses the global search field, letting you jump straight to searching for an issue by key, summary text, or other indexed fields. |
| Go to a specific board | G then B (then select from list) | G then B | Opens a quick navigation menu to jump to a specific Scrum or Kanban board, useful for teams managing several boards across multiple projects. |
| Move to next issue in list | J | J | Moves focus to the next issue in the current list or backlog, letting you scan through issues sequentially using J/K similar to many other list-heavy web apps' conventions. |
| Move to previous issue in list | K | K | Moves focus to the previous issue in the list, the counterpart to J, together forming the standard up/down list navigation pattern Jira shares with several other developer-focused web tools. |
| Go to project backlog | G then then select Backlog from menu | G then B | Jumps directly to the current project's backlog view, distinct from the board navigation shortcut since backlog and active sprint board are different screens serving planning versus in-progress tracking respectively. |
| Open keyboard shortcut reference | Shift+/ (i.e. ?) | Shift+/ | Opens Jira's own in-app overlay listing currently active keyboard shortcuts for the screen you're on, useful since some shortcuts differ slightly between the backlog, board, and issue detail contexts. |
Frequently Asked Questions
Why does pressing 'i' to assign sometimes type into a text field instead?
Single-letter Jira shortcuts only activate when focus is on the issue list or detail view itself, not inside any text input. If your cursor happens to be in a comment box, description field, or search bar, letter keys type literally instead of triggering shortcuts — click outside any text field first, or press Escape to exit field focus.
What's the difference between J/K navigation and just scrolling?
J and K move a focus indicator between issues one at a time without necessarily requiring the page to scroll if the issue is already visible, and critically, they let you then trigger other single-letter shortcuts (like C to comment or I to assign) against whichever issue currently has that focus — scrolling alone doesn't set focus the same way, so shortcuts like M for comment wouldn't know which issue to target without first navigating to it via J/K or a click.
Do these shortcuts work the same in Jira Server as Jira Cloud?
Mostly, but not guaranteed identically — Jira Server and Data Center installations run on potentially older codebases with their own shortcut implementations, and some Cloud-specific UI features (and their associated shortcuts) may not exist at all in Server. If a shortcut fails consistently, checking which Jira edition and version your organization runs is a reasonable first troubleshooting step.
Does the quick-transition shortcut respect workflow rules, like required fields before moving to Done?
Yes — the quick-transition menu triggered by the period key still enforces whatever workflow validators and required-field rules an admin has configured for that transition, so if moving an issue to Done requires a resolution field to be set, you'll still be prompted for it through the same dialog rather than the shortcut silently bypassing that validation.
Can I customize which single-letter key triggers a given action?
Jira's core keyboard shortcuts are largely fixed defaults rather than freely remappable per user, unlike some IDEs or design tools that expose a full keymap editor; there are official Atlassian shortcut reference pages listing the current defaults per product area, which is generally the most reliable source if a specific binding seems to behave unexpectedly after an update.
Does creating an issue with the C shortcut let me set the issue type, or does it default to a Task every time?
The Create Issue dialog opened by C includes the full issue type selector (Bug, Story, Task, Epic, and any custom types your project defines), so you're not locked into a default type — it simply opens the same creation form faster than navigating there through a button, with all the same field options available. This flexibility is one of the reasons larger organizations with strict compliance workflows still find the keyboard-driven transition menu practical rather than a shortcut that risks skipping necessary process steps. Larger enterprise deployments in particular tend to lock down the more consequential shortcut-adjacent settings through admin-managed configuration rather than leaving them freely editable per individual user.
Is there a way to see all available shortcuts without leaving the app or checking documentation?
Yes, pressing Shift+/ (which produces a question mark) opens Jira's built-in shortcut overlay for whatever screen you're currently on, which is useful precisely because the available shortcut set can differ slightly between the backlog, an active sprint board, and an individual issue's detail view.