Managing Tags

The Tags admin page is organised into context tabs — one for each area of the product. Switch between tabs to view and manage tags for each context independently. Tags are tenant-wide: once created, they are available across all projects without any extra environment.

Context tabs

Navigate to Settings → Tags. The page shows four tabs:

  • Test Cases — tags for test cases in the test repository.
  • Test Runs — tags for test runs.
  • Explorations — tags for test sessions.
  • Automation — coming in a future release.

Each context has a completely independent set of tags. Tags with the same name can exist in different contexts without conflict. Use the search box on each tab to filter tags by name.

Automation is coming in a future release. Tags created in the Automation tab are saved, but usage tracking is not yet built, so every count on that tab reads zero. A note above the table says so.

Creating a tag

Select the context tab you want to add a tag to, then click New tag. The dialog asks for two things: an icon (with its colour) and a name, and shows an Appears as preview of the finished tag as you go.

Name

Tag names must be 2–50 characters and can contain only letters, numbers, hyphens (-), and underscores (_). Spaces are not allowed.

Name format: Letters, numbers, hyphens, and underscores only — no spaces.
Valid: Bug, High-Priority, API_Test, v2-Release, Regression
Invalid: High Priority (space not allowed), -Bug (cannot start with a separator), Test--Case (consecutive separators not allowed)

Names are unique per context (case-insensitive), and the dialog checks as you type — a name already taken in that context is reported under the field before you submit. Two Test Cases tags cannot share the same name, but a Test Cases tag and a Test Runs tag can have the same name independently.

Icon and colour

The icon and its colour are one decision, taken in one picker. Open it from the Icon control: the panel holds the built-in icon library — the same one used throughout the product, with a filter box — and a row of 18 colour presets beneath it. Pick an icon, pick a colour, and the Appears as preview updates. There is no free-form hex entry; the presets are the palette.

The colour is applied to the icon everywhere the tag appears, making tags easy to recognise at a glance.

Tags are available to all projects. There is no project assignment step — a tag created here is immediately usable in every project across your workspace.

Editing a tag

Open the actions menu at the end of a tag’s row and choose Edit tag…. Name, icon and colour are all editable.

Usage count

The Used column shows how many test cases or runs (depending on context) currently have the tag applied; a tag nothing points at reads Not used. The count excludes deleted items and updates as project members add or remove the tag.

Deleting a tag

Open the row’s actions menu, choose Delete tag…, and confirm. The dialog names the tag and warns that it cannot be recovered.

Deleting a tag removes it from everything it is applied to. All associations with test cases, runs, and sessions are removed immediately. There is no replacement or migration step, and this action cannot be undone.