Skip to content
API reference Go to app

Labels Overview

2 min read

Labels help teams organize project work with lightweight categories. They are useful for grouping items by product area, release theme, test area, triage status, feature, customer, or any other classification your team uses.

Labels are managed at the project level and can be reused across supported work items in that project.


Hawzu supports labels across several project areas.

You can apply and filter labels on:

  • Test cases
  • Requirements
  • Releases

The Labels page also tracks usage counts for:

  • Test cases
  • Requirements
  • Releases
  • Executions
  • Defects

Usage counts help you understand where a label is being used before you edit or delete it.


Use labels when you need a flexible way to group work without changing the main structure of the project.

Labels are helpful for:

  • Filtering lists quickly
  • Grouping related work across folders or sections
  • Highlighting release scope
  • Marking product areas, teams, or feature areas
  • Creating lightweight triage categories
  • Improving reporting and review workflows

Labels are intentionally simpler than custom fields. Use labels for quick, reusable categories. Use custom fields when you need structured values with a defined field type.


Each label has:

  • Name
  • Color
  • Preview

The color controls how the label appears in lists and label pickers. A label can also use a transparent style when you want a neutral look.


The project Labels page is the central place to view and manage labels.

From the Labels page, you can:

  • Create labels
  • Search labels by name
  • Filter by creation date
  • Sort by name or creation date
  • Show or hide table columns
  • View usage counts
  • Open label details
  • Duplicate labels
  • Export label data

Each row shows the label name, color, usage summary, created date, and available actions.


Opening a label shows:

  • Label name
  • Label color
  • Label preview
  • Usage details

The usage details show linked test cases, requirements, and releases when the label is used in those areas.


Label actions depend on your project permissions.

Depending on your role, you may be able to:

  • View labels
  • Create labels
  • Edit labels
  • Delete labels

If a button or action is unavailable, your project role may not include the required permission.


When using labels:

  • Keep names short and easy to scan
  • Use consistent naming across the project
  • Avoid creating several labels with the same meaning
  • Choose colors that make important categories easier to recognize
  • Review usage before renaming or deleting labels
  • Use labels for flexible grouping, not for data that needs strict validation