Case Detail
Think of each test case as a case file. The cover sheet shows metadata at a glance — template, state, tags, who created it. Inside are the detailed fields and steps. The appendices hold comments, execution results, change history, and linked issues. The detail view brings all of this together in one place.
Two ways to view a case
Click any row in the case table to open the case. You have two viewing modes:
| Mode | How it works | Best for |
|---|---|---|
| Side panel | Opens as a resizable panel on the right side of the table. The table remains visible so you can click other cases quickly. | Browsing through cases, quick reviews, comparing cases side by side with the table. |
| Full-page view | Click the expand button to open the case in a dedicated full-width page. The table is hidden. | Detailed reading, editing complex fields, reviewing long step sequences, working with comments and history. |
Switch between modes at any time. The side panel is resizable — drag the left edge to adjust its width.
Case header
The header bar at the top of the detail view shows:
- Case number — the auto-assigned identifier (e.g.
C-123). - Title — the case name.
- Edit button — opens the editing form (requires EDIT_TEST_CASES permission).
- Expand / collapse button — toggles between side panel and full-page view.
- Close button — closes the detail view and returns to the table.
- Previous / Next arrows — navigate to the adjacent case in the current table order without closing the panel.
Metadata section
Below the header, the metadata section displays the case’s core properties. Think of this as the “cover sheet” of the case file — everything you need to understand the case at a glance.
| Property | What it shows |
|---|---|
| Template | The repository template used by this case. Determines which fields appear. |
| State | Current lifecycle state (e.g. Draft, Ready, Approved) with its icon and colour. |
| Tags | Applied tags shown as coloured chips. |
| Environments | Assigned platform configurations (e.g. Chrome – Windows 11, Safari – macOS). |
| Estimate | Time estimate in human-readable format (e.g. 1h 30m). |
| Folder | The folder path where this case lives in the folder tree. |
| Created | Date, time, and user who created the case (with avatar). |
| Updated | Date, time, and user who last modified the case (with avatar). |
Template fields
Below the metadata, the case displays all fields defined by its template. Fields are rendered in read-only mode, matching the field type:
| Field type | How it displays |
|---|---|
| TEXT (rich text) | Formatted HTML with headings, lists, bold, italic, links, and inline images. |
| STRING | Plain text on a single line. |
| INTEGER / FLOAT | Numeric value. |
| DATE | Formatted date string. |
| CHECKBOX | A checked or unchecked indicator. |
| DROPDOWN | The selected option label. |
| MULTI_SELECT | Selected options shown as chips. |
| LINK | A clickable URL. |
| STEPS | Numbered step cards displayed vertically with connecting lines. Each card shows the step’s subfield columns (e.g. Step, Expected Result, Notes). |
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.
Attachments
If the case has attachments, they appear as a list of files with their names, sizes, and download links. Inline images embedded in rich text fields are displayed directly within the field content.
Tabs
The lower section of the detail view is organised into tabs — the “appendices” of the case file. Each tab provides a different lens on the case’s activity and relationships.
Comments tab
A chronological thread of comments attached to the case. Use comments for team discussion, review notes, or clarifications without modifying the case itself.
- Add a comment — type in the rich text editor at the bottom and click Submit. Comments support formatting (bold, italic, lists, links).
- Edit a comment — click the edit button on your own comment to modify it.
- Delete a comment — click the delete button on your own comment. A confirmation dialog appears before deletion.
Comments show the author’s avatar, name, and timestamp. They are displayed in chronological order (oldest first).
Results tab
This tab shows execution results from test runs that include this case. Each result entry displays:
| Column | What it shows |
|---|---|
| Run name | The name of the test run where this case was executed. |
| Status | The execution result (e.g. Passed, Failed, Blocked) with icon and colour. |
| Executed by | The user who recorded the result (with avatar). |
| Environment | The platform configuration used during execution. |
| Timestamp | When the result was recorded. |
Results are read-only in the case detail view — they are recorded during test execution in the Cycles module. This tab gives you a complete execution history across all runs.
The Results tab is your test case’s track record. It answers the question “Has this test case ever failed, and when?” without leaving the case detail view.
History tab
A complete audit trail of every change made to the case. Each history entry shows:
- Field name — which field was changed.
- Old value — what the field contained before the change.
- New value — what the field was changed to.
- Changed by — the user who made the change (with avatar).
- Timestamp — when the change was made.
History entries are displayed in reverse chronological order (most recent first) and paginated at 50 entries per page. This tab is invaluable for understanding how a test case evolved over time and who made specific changes.
History captures everything. Title changes, state transitions, field value updates, tag additions, template switches — every modification is recorded with full before-and-after details.
Issues tab
Shows all external references (issues, tickets, stories) linked to this case. Issues are grouped by their integration source (e.g. Jira, GitHub, Azure DevOps). Each linked issue displays its key, title, and a clickable link to the external tracker.
To manage linked issues, see Editing & Managing. For more on how external references work, see External References.