Editing & Managing

Once a test case exists, you can update its fields, switch its template, manage attachments and linked issues, or delete it entirely. This page covers the day-to-day operations for keeping your test cases accurate and up to date.

Editing a test case

There are two ways to edit a case, depending on which viewing mode you are using:

Both methods provide access to all editable fields: title, template, folder, lifecycle state, estimate, tags, environments, and all template-defined fields including steps.

Editing requires the EDIT_TEST_CASES permission. If you do not see the Edit button, ask your workspace administrator to grant this permission to your role.

What you can edit

Every field that was available during creation can be modified after the fact:

• Title — update the case name.
• Folder — move the case to a different folder.
• Lifecycle state — transition the case (e.g. Draft → Ready → Approved).
• Estimate — adjust the time estimate.
• Tags — add or remove tags.
• Environments — assign or unassign platform configurations.
• Template fields — modify any field defined by the template, including rich text, dropdowns, steps, and more.

The case number (e.g. C-123) cannot be changed — it is permanently assigned at creation.

Changing the template

You can switch a case to a different template from the edit form. This is useful when your testing approach changes or when a template is updated.

Changing a template may cause data loss. When you switch templates, TestOrchestrator compares the fields in both templates. Fields that exist in both templates (same field, same type) keep their values. Fields that only exist in the old template lose their values permanently. A confirmation dialog warns you before the switch is applied.

For example, if you switch from a template with a “Priority” dropdown to one without it, the priority value is lost. But if both templates share a “Description” rich text field, that content is preserved.

Managing attachments

Attachments can be added or removed during editing:

• Add attachments — drag files onto the attachment area or click to browse. Supported formats include PNG, JPG, GIF, WebP, PDF, CSV, Excel, Word, PowerPoint, and plain text files.
• Remove attachments — click the remove button next to any attachment to detach it from the case.
• Inline images — paste or drag images directly into rich text fields. These are stored as attachments but displayed inline within the field content.

Removing an attachment from a case does not affect test runs. If the case was already executed in a test run, the run’s snapshot retains its own copy of the data.

Managing linked issues

Link external tracker items (Jira tickets, GitHub issues, Azure DevOps work items, etc.) to provide traceability between test cases and the features or bugs they cover.

• Add a link — in the Issues section of the edit form, select the integration source and enter the issue key or URL. The issue’s title is fetched automatically.
• Remove a link — click the remove button next to a linked issue to unlink it. This does not delete the issue in the external tracker.

Linked issues appear in the Case Detail Issues tab and can be used as a filter criterion in Browsing & Search. For more on configuring integrations, see External References.

Deleting a test case

You can delete a case from two places:

• Table row — right-click the row (or click the three-dot menu) and select Delete.
• Detail panel — click the delete option in the case header menu.

Before deletion, a confirmation dialog shows what will be permanently removed.

Deletion is permanent. Deleting a test case removes the case and all of its associated data: field values, attachments, comments, and change history. If the case is included in any active test runs, it is removed from those runs as well. This action cannot be undone.

Permissions reference

The following permissions control editing and management operations:

For a complete permissions overview, see Test Cases Overview.