Browsing & Filtering

The EXPLORATIONS tab is a single-pane workspace with a toolbar that starts with the session-state scope tabs, optional facet chips, and three list layouts. The scope, search, filters and layout are reflected in the URL so filtered views are bookmarkable and shareable.

Toolbar

A breadcrumb above the list names the project and Explorations. The toolbar below it starts with the scope tabs, then (right-aligned):

• Search — filters explorations by title, cycle name, tag name or reference (EX-7). See Search.
• Filter — opens a Linear-style fly-out (keyboard shortcut f) with multi-select fields: state, cycle, environment, owner, tags, and template.
• Layout toggle — switch between grouped (default), flat, and board (Kanban by session state).
• New exploration — opens the composer modal (keyboard shortcut c; requires Create explorations permission). Deep links with ?new=1 also open the composer.

Search

The search field matches an exploration's title, its cycle name, its tag names, and its reference. The search term is stored in the URL so the filtered view persists across reloads.

Searching by reference

Every exploration carries a reference that is unique within its project — EX-7. Typing any of these forms finds that exploration:

A reference is scoped to one project: EX-7 means “exploration 7 in the project you are looking at”. A different project has its own EX-7.

The reference is not the number in the exploration's web address. /explorations/42 can be EX-7 — the address uses an internal record id, while the reference is the number assigned within the project. Quote the reference (EX-7) in tickets and chat; both keep working as links.

Scope tabs

A strip of pill tabs at the start of the toolbar narrows the list by session state — the built-in Planned → Live → Debriefed progression, not the exploration workflow states configured in Workflows (those stay in the Filter fly-out):

Every tab shows how many explorations it holds, All included, so opening on Live still tells you how many are planned or debriefed. A tab with nothing in it shows no number rather than a 0. The counts are of the whole project; search and filters narrow the list inside the scope you picked.

The scope is kept in the page address as ?scope=all, ?scope=planned or ?scope=debriefed (Live, the default, needs nothing). Reloading, pasting the link, or using the browser’s Back and Forward all land on the scope the address names. Older links that used ?facet= still open on the scope they named.

When the scope you picked holds nothing, the list names what it is hiding — for example No live explorations — 5 planned, 4 debriefed — with a Show all explorations link. No explorations yet only appears when the project has none at all.

From the keyboard: Tab onto the strip, then ← / → move between scopes (wrapping at the ends) and Home / End jump to All / Debriefed.

Facet chips

When active, multi-select facet chips appear below the tabs (cycle, owner, template, etc.). Each chip shows a count badge. Remove a chip to clear that facet. Chips combine with AND logic across facets and OR within a facet.

List layouts

Grouped

Rows clustered under cycle headers (or No cycle). Best for sprint-aligned views.

Flat

A single scrollable list sorted by recent activity.

Board

Kanban columns by session state, ordered Live, Planned, Debriefed — live work comes first. The board shows the columns the scope admits, so on the default Live scope it is a single Live column; pick All to see the three states side by side. The board is read-only: cards cannot be dragged between columns. Change an exploration’s state from its row menu (Start, Debrief, Resume) instead. The board has no bulk selection.

Row anatomy

The row menu

Hover a list row and a ··· button appears at its right. What it offers depends on the exploration’s state and on your permissions:

Exactly one of Start / Debrief / Resume is ever shown — they are the three edges of the same session-state progression and the state decides which one you get. Without Edit or Delete permission the menu button does not appear at all.

Bulk selection

In the Grouped and Flat layouts you can select several explorations and act on them at once. The Board layout has no selection — switch to Grouped or Flat first.

• Click a row’s checkbox to select or deselect it. The checkbox appears when you hover the row, and stays visible on every row once anything is selected.
• Shift-click a second checkbox to apply that click to every exploration between the two. Shift-clicking an unticked row selects the span; shift-clicking a ticked one deselects it.
• The checkbox on a cycle header (Grouped layout) selects every exploration in that cycle, and clears them when all are already selected. It shows a dash when only some are.

A bar appears at the bottom of the screen with three things on it:

• N selected, with a × that clears the selection. Esc clears it too, once no menu or dialog is open.
• Move to cycle — the one action on the bar itself, listing No cycle first and then the project’s open cycles. Completed cycles are not offered as a destination, though explorations already in one can still be moved out. Once there are more than four choices, a Search… box at the top narrows the list by cycle name as you type; the arrow keys and Enter pick from what is left.
• Actions — opens a command palette with everything else. Press A to open it from the keyboard (not while you are typing in a field, and not with ⌘, Ctrl or Alt held). Esc inside the palette steps back one level, then closes it.

The palette groups its actions into four sections. The Lifecycle actions only appear for states present in the selection, and each one counts what it will act on — Start 2 planned sessions, with an of 5 hint when the rest of the selection is in other states — so a mixed selection never needs trimming first.

Each action is one change with one toast, and the rows change the moment you pick. Most actions send one request for the whole selection; Debrief with a shared summary may send two, so that explorations which already have a write-up keep it. A selection of more than 200 is sent in batches of 200 for you.

Undo and the receipt

Every action ends in one toast just above the bar — Moved 3 explorations to Sprint 4, Time box set to 60m on 4 explorations, Debriefed 2 sessions. For cycle, owner, environment, time box and label changes, and for Debrief and Resume, the toast carries an Undo that puts each exploration back to its own earlier value. Once the toast has gone, a N bulk changes · reversible pill in the same place lists your bulk changes with a Revert button each, as it does on Test Cases. Start and Delete have no Undo. The Undo appears once the server has accepted the change, and a change the server refused is never listed. If an Undo itself is refused, a Couldn’t undo toast says so and stays until you press Retry or close it; the change stays in the pill, and the toast goes away once the change is reverted from there. Every Undo on this page is itself an edit, so it needs the same Edit explorations permission as the change — unlike Test Runs, where undoing a re-run is a delete and needs Delete test runs.

If the server refuses some of the selection, the toast says so in the error tone — Moved 3 of 4 explorations to Sprint 4 — 1 failed, with the reason when every refusal agrees on one — and only the refused rows go back on screen.

Selections the view is hiding

A selection survives switching scope tab, searching and filtering. If some selected explorations are no longer on screen, the note above the bar says 2 selected explorations are hidden by this view — still included. Every action applies to the whole selection.

Who sees which actions

Actions you can’t take are left out, not greyed out. Move to cycle, the Lifecycle actions and the Edit actions need Edit explorations; Delete needs Delete explorations as well. Without Edit explorations the palette offers only Copy IDs and Export CSV, with a note that editing needs exploration edit access.