A project is an independent repository of suites, test cases, runs, milestones, and defects. The Projects screen is your organization’s landing page: a directory of every project you can access, with at-a-glance health metrics and quick navigation into each one.
Reaching the screen
Sign in and you land on /projects. You can also click Projects in the top navigation from anywhere
in the app.
Two view modes
The directory renders the same paginated set of projects in either of two layouts, switched with the view toggle at the top right:
- List — a compact row per project. This is the default on your first visit.
- Cards — a responsive grid of project cards, denser on metrics and the team.
Your choice is remembered per browser (it persists across reloads), and it applies to both the directory and its loading, empty, and no-results states. Switching modes never re-fetches — it only re-draws the projects already on the page.
Per-project metrics
Every project shows the same four health metrics in both modes, computed live from the project’s data:
| Metric | Meaning |
|---|---|
| Cases | Active (non-archived) test cases in the project |
| Runs | All test runs, with a “{n} in progress” qualifier for runs that are still open |
| Defects | Unresolved defects (open or in progress). This metric is warn-highlighted when greater than zero, and the count is always shown as a number so the warning never relies on color alone |
| Milestones | Live (non-deleted) milestones in the project |
The team avatar-stack
Each project shows a small stack of overlapping member avatars — the project team — with a “+N” indicator when the team is larger than the avatars shown.
What the team reflects today. Under the current opt-out access model, every member of your organization has access to every project, so each project’s team stack shows the whole active organization. This is the honest current behavior, not a bug. When project-level access controls begin revoking members from specific projects, each stack will automatically narrow to that project’s members with no further changes.
Filtering
The filter row offers:
- Search — type to filter projects by name. The term is reflected in the URL so a filtered view is shareable and survives a reload.
- Member — filter the directory to projects a selected member can access. The selection is encoded in
the URL as a
memberUlidset, so a filtered link reproduces the same view when opened fresh.
Member filter today. Because every organization member currently has access to every project (see the note above), the member filter does not narrow the list yet. It is wired to the same access source as the team stack, so it will start excluding projects automatically the moment project-level access revocations exist.
- Test runs — filter to projects that have no runs (
Without runs), have at least one active run (Has active runs), or have at least one run of any state (Has any run). - Defects — filter to projects that have at least one unresolved defect (
Has defects) or no unresolved defects (Without defects). - Milestones — filter to projects that have at least one milestone (
Has milestones) or no milestones (Without milestones). - Cases — filter to projects that have at least one test case (
Has cases) or no test cases (Without cases).
These filters compose with each other, with the Member filter, and with the search term — all active conditions are applied together (AND across filters, OR within a filter’s selected options). Each selection is encoded in the URL so filtered views are shareable and survive a reload.
When a search or member filter matches no projects, the directory shows a no-results state with a Clear filters action that removes both the search term and the member selection at once. This is distinct from the empty state shown when your organization simply has no projects yet, which offers a Create first project action (for organization owners and administrators).
Favorites
Click the star on any project to add it to your favorites. Favorited projects float to the top of the page you are viewing, keeping their relative order otherwise. Favorites are stored per user and per organization in your browser.
Favorites sort within the current page only. A favorite that lives on another page of a large directory is not pulled forward to the first page. For the typical single-page portfolio this is invisible; it only matters once a directory is large enough to paginate.
Pagination
When your organization has fewer than ten projects, no pager is shown — the directory is a single page. With ten or more, the pager appears below the directory: the rows-per-page selector and the range summary always show, and the previous/next and page-number controls appear only once the directory spans more than one page. Changing the page requests that page of projects.
Navigating tables with the keyboard
Across Probara’s list screens rendered as a table — test runs, workspace members, and others — every row
that opens a detail can be reached without a mouse: press Tab until the row is focused, then press
Enter or Space to open it, the same as clicking. A row’s own controls (an actions menu, a remove
button) still work independently and never trigger the row’s own navigation.
Creating a project
Organization owners and administrators see a New project button in the header (and a Create first project action in the empty state). Members and viewers can browse the directory but do not see the create action.
Project settings
Open Settings from the project sidebar or choose Edit on the projects list (⋯ menu). You can review Name, Project ID, and Description for any member of the organization.
Only organization owners and administrators can save changes. Members and viewers see the same fields read-only.
Owners and administrators can also upload, change, or remove the project picture from settings. The image appears in the project sidebar, the projects list, and the settings header. Members and viewers see the picture (or initials fallback) but cannot change it. Allowed formats: PNG, JPEG, or WebP, up to 5 MB.
The Project ID is the uppercase prefix used in test case and suite display IDs (for example ACME-14). Changing it updates those prefixes immediately and breaks old /projects/<old-id> URLs and bookmarks—plan integrations and shared links before renaming.