Browsing Projects

Projects — the second entry in the sidebar, below Home — lists every project you can open, filling the window edge to edge. It is one list, not a set of tabs: active and completed projects sit together, and you choose how they are grouped, sorted and shown.

Not the admin view. This page lists the projects you can open, and lets you pin, edit and complete them. Administrators who need every project in the workspace — the access default and its exceptions, and delete — should use Settings → Projects instead. At the plan’s project limit this page shows the same warning strip the admin list does, and New project is disabled with the same reason. See All Projects (Admin).

The toolbar

One strip under the page heading carries everything that changes what you are looking at:

The scope pills

Four pills decide which projects are in play. The selected one carries a count; the others do not, because four numbers competing to be read is three too many.

• All projects — everything you can open.
• Active — projects still in use.
• Completed — projects marked finished.
• Pinned — the projects you pinned to the sidebar, active and completed alike.

The counts follow whatever you have typed in the search box, so they always describe what you would actually see.

Search

Typing filters the list as you go, matching the project name or its summary — searching for ledger finds a project called Payments whose summary mentions the ledger. A clear control appears in the field once there is something to clear.

When nothing matches, the list is replaced by the query you typed — No projects match “…” — over the reminder that “Search looks at project names and descriptions.”

Display options

The control at the right of the toolbar opens a panel holding every choice about how the list is drawn. The choices are yours alone, and they are remembered on your account — you will find the same layout on another machine. Reset to defaults at the foot puts everything back.

List or cards

Two layouts, and until you choose one the page decides by size:

Cards are a good door for a handful and a poor table at forty. Picking List or Cards yourself overrides the size rule from that moment on, in both directions.

Grouping and ordering

Grouping offers Status (the default), Cycle, or No grouping. Grouped by status you get an Active heading and a Completed heading, each with its own count and each collapsible; an empty group is not drawn at all.

Grouping by status is quietly dropped on the Active, Completed and Pinned scopes — a single heading repeating the pill you just pressed says nothing. Grouping by cycle is not: it says something those scopes do not.

Grouping by Cycle

Cycle sorts the list into four states, in that order — most urgent at the top:

A project appears exactly once, under the most urgent state it is in. A project running one past-due cycle and two healthy ones sits under Past due and is counted there only — so a heading’s count is a count of projects, never of cycles. An empty heading is not drawn at all, so a workspace with nothing late never sees the word.

There is deliberately no Completed heading. A project has its own completed state, shown by the Status column and the Active/Completed pills, and two different meanings of that word in one list would be a trap. A project whose cycles have all been completed simply has no cycle running, so it reads No active cycle.

No active cycle is always the last heading, whatever the others are doing. Projects whose figures could not be fetched at all land there too, and their Cycle cell still reads as a dash rather than claiming anything.

Cycles are counted across the project rather than read off the project record, so for a moment after the rows appear the list is not yet grouped — it shows as one ungrouped list, and the headings appear once, together, when the answer arrives. It deliberately does not put every project under “No active cycle” first and then rearrange: that would be a claim about every row that the next moment contradicts.

Ordering offers Name, Cases, Updated, Created or Status, with an arrow beside it to reverse the direction.

Sorting from the column heads

In the list layout you do not have to open the panel to re-sort: the Name, Status, Cases, Updated and Created heads are buttons. Click one to sort by that column, click it again to reverse. The panel and the heads are the same setting, so one always reflects the other, and the active head shows its direction. Open runs, Pass rate and Cycle are not sortable — their heads are labels.

Sorting by Cases or Updated while those numbers are still arriving parks the rows that have not answered yet at the end, in both directions, rather than guessing a zero for them. They settle in behind the known rows once, instead of the whole table rearranging itself when the numbers land.

Sorting and the scope pills are not remembered between visits — they are how you are reading the list right now, and coming back a week later to someone’s forgotten filter helps nobody.

Show completed

A switch, on by default. Turning it off drops completed projects from the All projects view and its count together. It is deliberately inert on the Completed and Pinned scopes, where it would contradict the scope you explicitly chose.

Columns

Under Display properties the panel lists every column the list can show, with a running count of how many are on and a Find a property… box for when the list is long. Seven are offered; the project’s name and its row menu are always there and are not among them.

Five are on to begin with — Cases, Open runs, Pass rate, Cycle and Updated. Status and Created start off: the list is grouped by status already, so a Status column repeating “Active” on every row under an “Active” heading is the same fact twice, and Created is the less-consulted of the two dates. That is the starting point for someone who has never chosen. If you have picked your own columns, they are what you keep — the default applies to a fresh account, not to your account.

Columns also drop themselves when there is not enough room — narrow the window, or widen the sidebar, and they go in a stated order so the project name never gets squeezed and the list never scrolls sideways: Created first, then Updated, Open runs, Cycle, Status and Cases, with Pass rate the last to go. A dropped column is still listed in the panel and comes back as soon as the space does.

What the numbers mean

Five of the seven columns are counted across the project rather than read off the project record, and they arrive a moment after the rows do — a short placeholder bar sits in each cell until they land, sized so the row does not move when the number replaces it.

Two marks are worth telling apart. An em dash (—) is never an error and never a zero. In Open runs it means there are none open — an empty backlog reads better as nothing than as a counted nothing. In Cycle it means nothing is running and nothing is scheduled. Where a project’s figures could not be fetched at all, every one of its derived cells reads as a dash, and each one says which fact is missing when read aloud.

Pass rate

Pass rate is not the result of one run. It is the latest recorded result for each test case, rolled up over the whole project, so a case re-run yesterday counts once, as it stands today.

The percentage is measured against every case in the project, not against the cases that happened to be run. A project where one case passed and nine hundred were never touched reads as a low number, which is the honest reading; dividing by the cases that were run would have it read 100%.

Point at the cell, or tab to it, and a tooltip spells the whole thing out in words — “Latest status across 412 cases: 240 passed · 61 failed · 108 untested. Last run 2h ago.” It opens on hover after a short pause and immediately on keyboard focus, and closes on Esc or when you move away. A project that has never been run ends “Never run.” rather than naming an age.

The cell is a stop on the keyboard path for that reason. Because it is, clicking the Pass rate cell itself does not open the project — anywhere else on the row still does, the same way the row’s … menu behaves.

Screen readers get that identical sentence from the cell without opening anything.

Blocked and Skipped are neither passed nor failed. A result in any status that is not a success or a failure sits in no bucket, so passed, failed and untested need not add up to the case count. When some cases are in that position the tooltip names them rather than leaving you to find the gap: “… · 3 in another status.” The clause appears only when there is actually a remainder to name.

A project where nothing has passed or failed yet reads No runs yet instead of 0% — a project nobody has tested and a project that fails everything are different facts and should not share a number.

Cycle

The Cycle cell names one cycle — the one that speaks for the project — and says where it stands, in the words of the state the grouping would put the project under. The four states are the same four described under Grouping by Cycle, whether or not you are grouping.

Amber is used for past due and for nothing else. An upcoming cycle is not a problem, and a full pipeline should not read like a full inbox. Colour is never the only signal either: the past-due cell says the word over, and read aloud it opens with “Past due cycle”.

Every countdown is measured in whole calendar days, so a cycle ending today reads due today all day rather than turning over at some hour of the afternoon — and it is the same rule the Past due badge on the Cycles pages uses, so the two can never disagree about a cycle ending today.

When a project has more than one cycle in the same state, the cell adds a +N marker for the others and the hover says which one you are looking at: “3 past due cycles — Hotfix 1.3.2 ends first”, or “2 upcoming cycles — Release 2.0 starts first”. With only one, the hover simply names the state: “Active cycle · 9d left”. The hover opens on hover and on keyboard focus, and closes on Escape. See Cycle Lifecycle for what makes a cycle active.

Rows and cards

However the list is drawn, each project shows its icon and name, its summary if it has one, and whichever columns are on. Clicking it opens that project’s dashboard.

The numbers are a list feature. A card carries the project’s name, its summary, its status and the date it was created — not Cases, Open runs, Pass rate, Cycle or Updated. Display properties is not shown at all while you are in the Cards layout, because there are no columns to choose. Switch to List to read the numbers.

• Completed projects are drawn greyed and italic, in place. They are not moved to a separate list and nothing about them is hidden.
• A pinned project carries a marker beside its name, announced as Pinned to the sidebar.

The row menu

The control at the end of each row opens a short menu. What is in it depends on the project and on you:

Someone without edit permission gets a menu of exactly one entry, Pin to sidebar — pinning is a personal convenience, not an administrative act.

Editing a project from here

Edit project opens the project editor on its own page — the same page New project opens, and the same one Settings → Projects and the sidebar row menu open. There is no shorter dialog any more: the project’s name, icon, summary, completed switch, default access and exceptions are all on that one page, behind one save bar. Saving brings you back here.

Deleting a project is not offered here, and neither is your plan’s project limit; both live on Settings → Projects. See Create a Project for the editor itself and Project Access for the two access panels.

Pinning

Pinning takes effect immediately: the project appears in the sidebar as you watch, with no save and no reload. Unpinning is the same in reverse. Your pins are yours — nobody else’s sidebar changes.

Marking a project completed

Completing a project is a reversible status change, not a deletion. The project and everything recorded in it stay exactly where they are; it simply leaves the project switcher and stops being offered for new runs.

The row updates at once — greyed, moved under the Completed heading, both group counts corrected — and a message confirms it: “<name> marked completed”, with an Undo beside it. Undo puts the project straight back and confirms that too: “<name> reopened”.

The Undo only lives as long as the message. After it has gone, Mark active in the same row menu does the same job.

Completing a project does not free a slot against your plan’s project limit — every project you have not deleted counts. At the limit the page says so, and says what to do about it, rather than leaving you to discover it halfway through creating one. See All Projects (Admin).

Completing is not deleting. There is no delete on this page. Deleting a project is permanent, unrecoverable, and lives on Settings → Projects behind a confirmation that makes you type the project’s exact name. See All Projects (Admin).

Empty states

The sample project

While the workspace has no projects and you are allowed to create one, a card beneath the create prompt asks Not sure where to start? and explains that “The sample project arrives with test cases, runs and explorations already in it.” Try the sample provisions it and takes you straight to its dashboard.

The card does not come back once a sample project exists in the workspace.