Creating a Case
Click the New Case button to open the case creation form. The form guides you through required metadata, template-driven custom fields, file attachments, and optional external issue links.
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. Required fields are printed in bold — you cannot file the card until they are completed. 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.
- Enter a title — a short, descriptive name for the test case.
- Select a template (the project’s default template is pre-selected). This determines which custom fields appear.
- Choose a folder (defaults to the currently selected folder in the tree).
- Set the lifecycle state (the default state is pre-selected).
- Fill in any template fields — text, steps, dropdowns, attachments, and more.
- Optionally add tags, environments, an estimate, attachments, or external issue links.
- Click Create.
The new case appears in the table with an auto-generated case number (C-1, C-2, etc.) unique within the project.
Core metadata fields
| Field | Required | Description |
|---|---|---|
| Title | Yes | The case name shown in the table and detail panel. |
| Template | Yes | Determines which custom fields appear on the form. The project’s default template is pre-selected. See Repository Templates. |
| Folder | Yes | The folder this case belongs to. Defaults to the currently selected folder. |
| Lifecycle State | Yes | The current state (e.g. Draft, Ready, Approved). See Lifecycles. |
| Estimate | No | Expected execution time. Accepted formats: 1h 30m, 90m, 30s, 1:30:00. |
| Tags | No | Labels for categorisation and filtering. See Tags. |
| Environments | No | Platform configurations the case applies to. See Environments. |
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 Repository 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.
- Drag to reorder — grab the handle on the left side of any step and drag it to a new position.
- Insert below — click the + button on any step to add a new step immediately after it.
- Delete — click the trash icon to remove a step.
- Steps are visually connected with numbered circles and vertical lines.
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 (Step, Expected Result, Notes, etc.) are configured by an admin when setting up the field. See Field Types for details on STEPS configuration.
Switching templates
If you change the template after filling in fields, a confirmation dialog appears. Fields that exist in both the old and new templates keep their values. Fields that only exist in the old template lose their values permanently.
Switching templates can erase data. If the new template does not include a field from the old template, any value you entered in that field is lost. Review the confirmation carefully.
Attachments
You can attach files to a case in two ways:
- Case-level attachments — drag files onto the attachment area or click to browse. These appear as downloadable files on the case.
- Inline images — paste or upload images directly into rich text fields (Text or Steps). These are embedded in the field content.
Supported file types: PNG, JPG, GIF, WebP, PDF, CSV, Excel, Word, PowerPoint, TXT.
Attachments are saved with the case. If you upload files but cancel the form without saving, the uploads are automatically cleaned up.
External issue links
If you have the Manage external references permission, you can link external tracker items (Jira issues, GitHub issues, etc.) to the case during creation. See External References for details on setting up integrations.
Saving
Click Create to save. The form validates that:
- Title is not empty.
- A template is selected.
- A folder is selected.
- A lifecycle state is selected.
- All required template fields are filled in.
- The estimate format is valid (if provided).
If validation fails, error messages appear next to the relevant fields. Fix them and try again.