Creating a Case
Click New case — or just press C — to open the composer. It is the same side panel you use to read a case, in draft mode, so creating one is a couple of keystrokes rather than a form to fill in.
Think of it as filling in a recipe card
The template is the card format — some recipes need an ingredients list, others need a tools section. Fields are the blanks you fill in. Switching to a different card format (template) may mean some blanks disappear and new ones appear.
Step-by-step
- Click New case on the Test Cases page, or press C.
- Enter a title — a short, descriptive name for the test case.
- Adjust the properties if you need to: State, Folder, Template, Estimate, plus any properties your template defines. Sensible defaults are pre-filled, and the folder starts as the one you are currently browsing — or Unfiled if you are not in a folder.
- Optionally add Labels.
- Press ⌘Enter (or click Create case).
The new case appears with an auto-generated case number unique within the project, and the panel switches straight to the real case so you can carry on writing.
Steps, prose fields, and attachments are added after you create. The composer deliberately leaves them out — they attach to a case that exists, and a case does not have an identity until you create it. Create first (it takes one keystroke), then write.
A draft with content will not vanish silently. If you have typed anything, closing the composer — by the ×, Cancel, Esc, or clicking away — asks you to confirm before discarding it.
Core properties
| Field | Required | Description |
|---|---|---|
| Title | Yes | The case name shown everywhere the case appears. |
| Template | Yes | Determines which fields the case carries. The project’s default template is pre-selected. See Test Case Templates. |
| Folder | No | The folder this case belongs to. Defaults to the folder you are browsing; leave it alone outside a folder and the case is filed under Unfiled. See The Folder picker. |
| State | Yes | The lifecycle state (e.g. Draft, Ready, Approved). See Lifecycles. |
| Estimate | No | Expected execution time. Accepted formats: 1h 30m, 90m, 30s. |
| Labels | No | Tags for categorisation and filtering. See Tags. |
The Folder picker
The Folder row opens the project’s folder tree, indented by depth, with the folder the case is currently in check-marked. Unfiled sits at the top as a destination in its own right — picking it is how you take a case back out of a folder without putting it in another one.
Past four folders the picker gains a Search folders… box; type to narrow the tree and press Enter to take the first match. Typing hides the Unfiled row, which is a destination rather than one of the folders you are searching.
If you have the Manage folders permission, the picker also creates folders inline: type a name that matches nothing and take the Create folder “…” row. The folder is created at the top level and the case is filed into it in the same gesture.
A folder is not required to create a case. A project with no folders at all can still have its first case written in it — the composer’s Folder row reads Unfiled and the server files the case there. See Unfiled.
Unfiled is offered only where it exists. The bucket is created the first time a case is created without a folder, so in a project where that has never happened, an already-filed case has no Unfiled row to move back to. It appears once the project has one.
Creating a case through the API or an MCP agent still requires a folder. The optional folder is a behaviour of the app’s own composer; the MCP
create_test_casetool takes a folder argument and will not create a case without one.
Template fields
Below the core metadata, the form shows custom fields defined by the selected template. These fields are configured by an admin in Fields and assembled into templates in Test Case Templates.
The following field types are available for test cases (see Field Types for full details):
| Type | Input |
|---|---|
| Text | Rich text editor with formatting, links, and inline images |
| String | Single-line text input |
| Steps | Structured step editor (see below) |
| Checkbox | Boolean toggle |
| Dropdown | Single selection from predefined options |
| Multi-select | Multiple selections from predefined options |
| Integer / Float | Number input |
| Date | Date picker |
| Link | URL input |
Fields marked as required in the template must be filled in before the case can be saved.
The STEPS field
The STEPS field is unique to test cases and is the most powerful field type. It lets you define a structured, ordered sequence of test steps — each with configurable subfield columns like Step, Expected Result, and Notes.
How it works
- Each step is a numbered row with one or more subfield columns.
- Each cell uses a rich text editor — you can add formatting, links, and paste images directly.
- Add — click Add step to append a row. A newly added row is not saved until you type into it, so an accidental click costs nothing.
- Reorder — use the Move step up and Move step down buttons on each row. They are disabled at the ends of the list.
- Delete — click the trash icon on a row. A toast names the step that went, and ⌘Z (or the toast’s Undo) brings it straight back.
- Steps are visually connected with numbered circles and vertical lines, and the editor shows a live step count above the list.
The columns come from your template. If your administrator configured only one steps subfield, you get a single action column; a second subfield becomes the expected-result column, and so on. There is no fixed Expected Result field — it is whatever your workspace named it. If a template has no steps configured, the editor says so rather than showing an empty grid.
Example: a 3-step login test
| # | Step | Expected Result |
|---|---|---|
| 1 | Navigate to the login page | Login form is displayed with email and password fields |
| 2 | Enter valid credentials and click Sign In | User is redirected to the dashboard |
| 3 | Check the welcome message | Dashboard shows “Welcome, [username]” |
The subfield columns above are an example. The real column names are configured by an admin when setting up the field — see Field Types for details on STEPS configuration.
Switching templates
The template is a property like any other, so you can change it at any time from the case’s Template row.
Switching templates can lose field values. Fields the new template does not include have nowhere to keep their value. If you switch by mistake, ⌘Z reverses it in the same session.
Attachments
You can attach files to a case in two ways, both after the case exists:
- Case-level attachments — use the Attachments section, which is available in the side panel as well as in the right-hand rail on the full page: click Add file, or drag files onto the drop area. These appear as downloadable files on the case.
- Inline images — paste or drag images directly into a rich text field or a step cell. These are embedded in the field content. Your edit waits for the upload to finish rather than saving a broken image.
Supported file types: PNG, JPG, GIF, WebP, PDF, CSV, Excel, Word, PowerPoint, TXT.
Removing an attachment is permanent — there is no undo. The × beside a file opens a confirmation dialog naming it, so a stray click cannot destroy evidence; the dialog opens on Cancel and Esc keeps the file. Confirming detaches it for good — ⌘Z will not bring it back, so download anything you might need first.
External issue links
Linked issues are added after the case exists, from the Linked issues section on the case. You need the Manage external references permission. See Case Detail and External References.
Saving
Press ⌘Enter or click Create case. You need a title, a template, and a state — both of the latter are pre-filled for you. A folder is optional: leave it and the case goes to Unfiled.
After that, there is no Save button anywhere on a test case. Titles, properties, and labels apply the moment you change them; steps and prose fields commit when you leave the field. A ✓ Saved receipt flashes to confirm, and ⌘Z undoes your last change. See Editing & Managing.