Labeling

As your test management scales, so does the challenge of staying organized. Labels offer a simple yet powerful way to tag both Test Cases and Tests with meaningful keywords, making it easier to group, search, filter, and report across TestRail.
They help teams streamline workflows, reduce admin overhead, and bring structure to even the most complex testing projects, without needing custom fields.
This feature includes full label management for Admins and Project Admins, as well as multi-select filtering, sorting, and reporting options.

Screenshot 2025-07-01 at 15.21.43.png

With labels, teams can:

  • Group related tests by, e.g., feature, environment, or sprint
  • Quickly filter and locate relevant test cases or test results
  • Improve report clarity without creating extra custom fields
  • Simplify cross-team collaboration by adding meaningful context

Use cases:

  • Tag tests with Smoke, Login, Mobile, or iOS to organize regression cycles
  • Use Backend, Performance, or Security labels to filter and assign test cases to specialized teams
  • Apply Feature: Checkout or Team: Payments, to generate targeted reports or exports

Label Management

Admins and project admins (with project add/edit access) can manage labels at the project level. To manage labels, go to Administration > Projects > [Project Name] > Label Management.

From this tab, users can:

Create Labels

Admins and project admins can create an unlimited number of labels. When creating a label:

  • It must be between 1–20 characters
  • It is case-insensitive
  • It may include letters (a–z), numbers (0–9), spaces (in the middle), and special characters
  • It must be unique within the project

To prevent duplication, an autocomplete dropdown will suggest existing labels as you type.

Edit Labels

When a label is edited, the updated label will automatically apply to all Test Cases and Tests using that label within the project. A warning message will confirm this before changes are saved.

This allows teams to easily refine naming conventions without manually re-tagging items.

Delete Labels

When a label is deleted, it is removed from all associated Test Cases and Tests. A confirmation modal will explain this before changes are applied.

Deleted labels are tracked in the audit log: Administration > Site Settings > Auditing

This ensures traceability and accountability for changes.

Permissions

  • Admins and project admins: Full label management (create, edit, delete)
  • Other users: Can create, assign, and remove labels within Test Cases or Tests pages, based on their case/result editing permissions.

Screenshot 2025-07-01 at 14.40.48.png

 

Using Labels

Labels can be created and/or assigned at both the Test Case and Tests within a Test Runs levels.

Test Case Labels

You can assign labels to Test Cases when:

  • Creating or editing a Test Case
  • Creating or editing a Test Case using Fast Track
  • Bulk editing Test Cases

You can assign up to 10 labels per Test Case. Labels are shown in alphabetical order in the Test Case details section.

These labels help group and identify Test Cases based on functionality, scope, platform, or ownership. For example:

  • Feature: Login
  • Browser: Safari
  • Team: Checkout

Test Case labels are also visible during Test Run creation and in reports, offering full visibility across the testing lifecycle.

 

For Enterprise users with Test Case Approval enabled, editing or assigning a label does not affect the case status.

 

Screenshot 2025-07-01 at 15.19.25.png

 

Test Labels (Within Test Runs) 

Labels can also be applied to individual Tests (executions of a Test Case in a specific run). This allows you to add context relevant to that run, without affecting the underlying Test Case.

You can assign up to 10 labels per Test.

To assign Test labels:

  • Navigate to Test Run & Results > Test Run X > Add Labels
  • Use bulk selection to apply the same labels to multiple Tests
  • Use the “Add Label” action from the single Test view or Fast Track

Test labels are shown above the Test Case details. These can include, for example:

  • Environment: Staging
  • Type: Regression

 

Test labels are run-specific and do not carry over to the Test Case.

 

Screenshot 2025-07-01 at 15.21.43.png


Filtering and Sorting by Labels

Labels can be used to filter and sort Test Cases and Tests across various views in TestRail. This helps you quickly surface the relevant items when navigating large suites or reviewing results.

Filtering

  • Filter by one or multiple labels at a time

  • Filtering supports both Test Case labels and Test labels

  • Available in:

    • Test Cases tab

    • Test Runs & Results tab

Sorting

  • Labels can be used to sort Test Cases or Tests (similar to sorting by references)

  • Sorting is available wherever columns are configurable

Reports Integration

Test Case and Tests labels are fully integrated into TestRail's core reporting tools. You can add labels as a column when generating reports, enabling deeper insights and filtering across key dimensions.

When selected, labels appear in the output of the generated report and any downloadable files (PDF/CSV).

This helps teams segment results by functionality, component, or any other relevant label.

Screenshot 2025-07-01 at 15.27.36.png

Importing, Exporting & Printing

Export

  • Test Case labels are included in all export types (CSV, Excel)
  • Labels appear as comma-separated values in a dedicated column

This applies to:

  • Test Case exports
  • Run exports
  • Plan exports
  • Milestone exports

Import

When importing Test Cases, labels in your CSV/Excel file are validated:

  • If the label exists: it is assigned to the Test Case
  • If it doesn’t exist: it is created and then assigned
  • If invalid: it is skipped without blocking the import

This allows seamless reuse of labels across teams and tools.

Print

Labels appear in all relevant print screens:

  • Test Case and Test Case view prints
  • Run, Plan, Milestone, and Suite prints

Both Test Case labels and Test labels are included when applicable.


 

Was this article helpful?
1 out of 2 found this helpful