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 Admin and they are immediately available across every project in the workspace.
How tags work
Tags are organised by context — each area of the product (Repository, Runs, Sessions, Automation) has its own independent tag library. A tag named High-Priority in the Repository context is completely separate from one named High-Priority in the Runs context. This keeps each area's tags focused and uncluttered.
| Context | Applied to | Status |
|---|---|---|
| Repository | Test cases in the test repository | Available |
| Runs | Test runs | Available |
| Sessions | Test sessions | Available |
| Automation | Automation scripts and configurations | Coming in a future release |
Automation context is coming in a future release. The tab is visible in the Admin UI and you can create tags there, but Automation usage tracking is not yet active.
Tenant-wide availability
Tags are available to every project in your workspace as soon as they are created. Unlike Statuses, Configurations, Workflows, and Milestones — which each have a project-assignment step — tags have no scoping mechanism. A tag created in Admin is immediately usable across all projects without any further configuration.
Getting started
- Go to Admin → Tags.
- Select the Repository or Runs tab for the context you want to add tags to.
- Click Add Tag and enter a name, choose an icon, and pick a color.
- 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 |