Tags
Tags are short, reusable labels — each with a name, icon, and color — that project members apply to test cases, runs, and sessions to categorise and filter their work. Create them once in Settings → Tags and they are immediately available across every project in the workspace.
How tags work
Tags are organised by context — each area of the product (Test Cases, Test Runs, Explorations, Automation) has its own independent tag library. A tag named High-Priority in the Test Cases context is completely separate from one named High-Priority in the Test Runs context. This keeps each area's tags focused and uncluttered.
| Context | Applied to | Status |
|---|---|---|
| Test Cases | Test cases in the test repository | Available |
| Test Runs | Test runs | Available |
| Explorations | Test sessions | Available |
| Automation | Automation scripts and environments | Coming in a future release |
Automation context is coming in a future release. The tab is visible in Settings and you can create tags there, but Automation usage tracking is not yet built, so every count on that tab reads zero. The tab says so above the table.
Tenant-wide availability
Tags are available to every project in your workspace as soon as they are created. Unlike Statuses, Environments, Workflows, and Cycles — which each have a project-assignment step — tags have no scoping mechanism. A tag created in Settings is immediately usable across all projects without any further environment.
Getting started
- Go to Settings → Tags.
- Select the tab for the context you want to add tags to.
- Click New tag, choose an icon and its colour, and enter a name.
- The tag is immediately available for project members to apply in all projects.
Who can manage tags?
| Action | Who can access |
|---|---|
| View the Tags admin page | Tenant Admin, Project Admin |
| Create, edit, or delete tags | Tenant Admin, Project Admin |