Command palette — Ctrl/Cmd + K, or the o key
This page is generated from docs/guide.en.md · Edit this page on GitLab
The palette itself is a core feature: it works with no plugin at all. Installed plugins (Links, Jenkins, Docker…) each add their own sources to it — the grid and free links, a job's page, a compose project.
The search field in the header opens the global palette, which searches everything at once: the grid's cells (“kibana staging”), free links, merge requests (by number or by words of the title), dev sessions (label, prompt or branch), watched tickets, note pages, open todos, and navigation actions. Enter opens — an external link in a new tab, an internal object in its own place.
- On opening, with nothing typed, it offers three short sections: Actions, Recent merge requests, Recent sessions, three of each. With no query everything scores the same, and it was the most numerous source — the grid's links — that took every slot: the palette opened on eight Kibana addresses without a single merge request. From the first letter the headings go away and ranking is by relevance again.
- Fuzzy search, accent- and case-insensitive —
generationfinds “Génération du rapport”, and the other way round. You abbreviate by words:kib prefinds “Kibana · preprod”, each word you type having to appear whole somewhere in the target. Dropping a letter inside a word (kbana) finds nothing, and that is deliberate: allowing gapped words all the way down into the database would push more than half the rows past the ranking, which would then have nothing left to sort with. The ranking itself favours what starts a word —apibrings up “api-core” ahead of “rapid”, which holds the same letters. - Ranked by frecency: what you open often and recently comes up. A plain counter would keep whatever you hammered last month at the top forever; a plain date would lose what you have opened every day for a year.
- The palette ACTS, it no longer merely navigates. Four everyday objects have joined it: a verifier (“Verify with payment integration” opens the branch-verification screen with that verifier picked), a Jenkins job attached to a repository (its sheet opens — never a run: a job deploys, it gets started deliberately), a compose project, and a saved git command, dropped into the Git commands field where the repositories remain to be chosen. The principle does not change: the palette can do nothing the screen cannot already do, it takes you to the right place and clicks the real button. A merge request is also found by its ticket key (
PROJ-1408), the way half a team refers to it. - The palette queries the server: it therefore sees everything, including what the current tab has not loaded — searching for a merge request from Docker works. Filtering happens in the database, not over a slice of it: a merge request three hundred older ones down is as findable as a fresh one. Only the answer is capped — at twelve rows, which is what a dropdown can show.