> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2026.1/user-guide/keyboard-shortcuts.md).

# Keyboard shortcuts

A list of keyboard shortcuts for use with SonarQube Server 2026.1.

## Global <a href="#global" id="global"></a>

|              |                 |
| ------------ | --------------- |
| **Shortcut** | **Action**      |
| `s`          | open search bar |
| `?`          | open help       |

## Code page <a href="#code-page" id="code-page"></a>

|              |                         |
| ------------ | ----------------------- |
| **Shortcut** | **Action**              |
| `↑``↓`       | select files            |
| `→`          | open file               |
| `←`          | return back to the list |

## Issues page <a href="#issues-page" id="issues-page"></a>

|                  |                                               |
| ---------------- | --------------------------------------------- |
| **Shortcut**     | **Action**                                    |
| `↑``↓`           | navigate between issues                       |
| `→`              | go from the list of issues to the source code |
| `←`              | return back to the list                       |
| `alt` + `↑``↓`   | to navigate issue locations                   |
| `alt` + `←``→`   | to switch flows                               |
| `f`              | do an issue transition                        |
| `a`              | assign issue                                  |
| `m`              | assign issue to the current user              |
| `i`              | change severity of issue                      |
| `c`              | comment issue                                 |
| `ctrl` + `enter` | submit comment                                |
| `t`              | change tags of issue                          |

## Measures page <a href="#measures-page" id="measures-page"></a>

|              |                         |
| ------------ | ----------------------- |
| **Shortcut** | **Action**              |
| `↑``↓`       | select files            |
| `→`          | open file               |
| `←`          | return back to the list |

## Rules page <a href="#rules-page" id="rules-page"></a>

|              |                                               |
| ------------ | --------------------------------------------- |
| **Shortcut** | **Action**                                    |
| `↑``↓`       | navigate between rules                        |
| `→`          | go from the list of rules to the rule details |
| `←`          | return back to the list                       |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/2026.1/user-guide/keyboard-shortcuts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.