Case Detail

Think of each test case as a case file. Its properties sit in one place — template, state, labels, estimate. Inside are the steps and the written detail. The appendices hold linked issues, attachments, comments, execution results, and change history. Everything is editable where it sits: there is no read mode and no edit mode.

Two ways to open a case

Click any row (or press Enter on a focused row) to open the case. There are two surfaces:

Click Open full page in the panel header to switch. It is a real link, so ⌘-click or middle-click opens it in a new tab, and the list’s filters and sort travel with you — the Back to test cases button returns you to exactly the view you left.

The side panel is a query parameter, not a page. The URL gains ?caseId= when you open one, so you can share a link that lands someone on the same case with the same list behind it.

Case header

In the side panel the header shows the case number (e.g. C-123), the ✓ Saved receipt as your edits commit, Open full page, a Case actions menu, and a close button.

On the full page the header shows a back button, a breadcrumb trail from All cases down to this case (with an overflow menu when the path is deep), the state pill, an Add to run button, and the Case actions menu.

There is no Edit button, and no Duplicate action. Every field is edit-in-place, so there is nothing to switch on. Case actions contains exactly one item — Delete case — and appears only if you have permission to delete.

Properties

Four properties are built in, and everything else comes from your template. Click any row to edit it; there is no pencil and no edit mode. An empty value shows as a dash.

Labels sit in their own section, and a meta line under the title shows who last touched the case and when.

Long-form text fields are not properties. Description, Preconditions, and any other rich-text field render as prose blocks in the body of the case rather than as rows in the properties list — a paragraph does not belong in a chip.

Template fields

A case renders each field its template defines, according to the field type:

Steps render as a visual sequence. Each step is displayed as a numbered card, connected by vertical lines to show the flow. This makes it easy to follow the test procedure from start to finish, even for cases with many steps.

Saving

There is no Save button. Titles, properties, and labels apply the moment you change them; prose fields and step cells commit when you move off the field. A ✓ Saved receipt flashes to confirm, and the panel footer states the contract outright: Saves as you leave each field · ⌘Z to undo.

Leaving the case — closing the panel, opening it full page, switching to another case, or closing the tab — commits anything still pending first, so an edit is never lost to navigation. If you pasted an image that is still uploading, the save waits for it rather than storing a broken reference.

Attachments

Attachments appear on both surfaces — in the rail on the full page, and in the side panel below the properties, outside the Steps/Details tabs so the file count is never hidden on the tab you are not looking at. Both are headed Attachments with a count. Add files with Add file or by dragging them onto the drop area. Inline images embedded in rich text fields are displayed within the field content instead.

Files attached to a custom field are listed in the same place, grouped under the field they belong to, so you can open them without hunting through the Details tab.

Removing an attachment is permanent — there is no undo. The × opens a confirmation dialog naming the file, which opens with Cancel focused; Enter confirms and Esc keeps the file. Once you confirm, the only way back is to upload the file again, and ⌘Z will not return it. If a run already executed this case, that run keeps its own snapshot, but the case does not get the file back.

Linked issues

The Linked issues section appears on both the side panel and the full page, and records what this case covers. Click Link issue to search your tracker, choose how the issue relates to the case (the Link as chips — Covers by default), and link it. Each row shows the issue’s status, title, key as an external link, and its relation, which you can change inline.

Unlink with the × on a row. It does not confirm — a toast tells you what went and ⌘Z re-links it.

Viewing this section needs View external references; linking and unlinking need Manage external references.

Undoing an unlink re-links the issue; it does not rewind time. You get the same issue back with the same relation, but as a new link record with a freshly fetched snapshot of the issue.

Activity

The full page ends with an Activity section — the “appendices” of the case file — filtered by four segments: All, Comments, History, and Results.

Comments

A thread of comments on the case, oldest first. Use them for team discussion, review notes, or clarifications without modifying the case itself.

• Add a comment — type in the rich text editor and post. Comments support formatting and pasted images.
• Edit a comment — choose Edit comment from its menu, then Save. Edited comments are badged edited.
• Delete a comment — choose Delete comment from its menu.

Deleting a comment takes effect immediately — there is no confirmation dialog and no undo. Which comments you may edit or delete is decided by the server against your permissions, not simply by whether you wrote them, so a moderator may see the option on someone else’s comment.

Commenting only needs view access. Anyone who can see the case can comment on it — you do not need edit permission to join the discussion.

Results

Execution results from test runs that include this case, newest first. This list is fetched only when you select the Results filter, and it is deliberately kept out of All so an active case’s run history does not drown its discussion. If the case has never been run you will see No run has recorded a result for this case yet. Each result entry displays:

Results are read-only here — they are recorded during test execution. This gives you the case’s complete track record across all runs, and answers “has this test case ever failed, and when?” without leaving the case.

History

An audit trail of changes to the case. Each entry shows who made the change, when, and the field’s value before and after, as old → new chips.

Entries are grouped the way the change actually happened: one save that touched three fields is one entry with three lines under a single avatar, not three separate rows. Consecutive changes by the same person within a couple of minutes are merged for display, keeping the original starting value so the entry reads as one edit rather than a flurry.

History is a record, not a rewind. There is no revert-to-version control — the ⌘Z undo stack covers your current session only. The feed shows up to the 100 most recent entries, and a steps change is summarised by shape (for example 3 steps → 4 steps) rather than printing the whole field.