Project Labels

Labels are lightweight, color-coded tags you attach to work items to add a second dimension of categorization beyond states and priorities. While states track where an item is in your workflow and priorities track urgency, labels describe what kind of work it is. Typical labels include "Bug", "Feature", "Documentation", "Performance", "UX", and "Tech Debt". Each project manages its own set of labels independently.

Create a label

1. Go to the project Settings > Labels.
2. Click Create Label.
3. Enter the label name (e.g., "Bug", "Feature Request", "Infrastructure").
4. Choose a color from the palette or enter a custom hex code.
5. Optionally select a parent label to create a hierarchical relationship.
6. Click Create.

The label is immediately available for use on any work item in the project.

TIP

Keep label names short and consistent. Agree on a naming convention with your team — for example, always use singular nouns ("Bug" not "Bugs") or always use a specific prefix pattern ("area/frontend", "area/backend").

Label colors

Every label has a color that appears as a small badge on work items. Colors help with quick visual scanning in list and board views. SetGet provides a preset palette, but you can also enter any hex color code.

Color category	Suggested usage
Red / Orange	Bugs, incidents, blockers
Blue / Purple	Features, enhancements, stories
Green	Tests, documentation, quality
Yellow / Amber	Warnings, needs attention, under discussion
Gray	Chores, maintenance, low-visibility items
Teal / Cyan	Infrastructure, platform, DevOps

To change a label's color after creation:

1. Go to Settings > Labels.
2. Click the color swatch next to the label.
3. Pick a new color.
4. The change is saved automatically and reflected everywhere the label appears.

Edit a label

1. Go to Settings > Labels.
2. Click the label name to edit it inline, or click the ... menu and select Edit.
3. Update the name, color, or parent label.
4. Save your changes.

Renaming a label updates it on all work items that currently have it applied. There is no need to reapply the label after renaming.

Delete a label

1. Go to Settings > Labels.
2. Click the ... menu next to the label.
3. Select Delete.
4. Confirm the deletion.

When you delete a label:

• It is removed from all work items that had it applied.
• If the label had child labels, the children become top-level labels (they are not deleted).
• The deletion cannot be undone.

WARNING

Deleting a label is permanent and affects all work items that use it. If you are unsure, consider renaming the label instead of deleting it.

Parent-child label hierarchy

Labels in SetGet support a single level of parent-child nesting. This lets you group related labels under a common parent for better organization.

How hierarchy works

• A parent label is a top-level grouping label (e.g., "Area", "Component", "Priority Area").
• A child label belongs to a parent (e.g., "Area/Frontend", "Area/Backend", "Area/API").
• Child labels appear indented under their parent in the label settings and in filter dropdowns.
• Filtering by a parent label includes all its children.

Create a child label

1. Go to Settings > Labels.
2. Click Create Label.
3. Enter the child label name (e.g., "Frontend").
4. In the Parent dropdown, select the parent label (e.g., "Area").
5. Choose a color and click Create.

Change a label's parent

1. Go to Settings > Labels.
2. Click the ... menu on the label and select Edit.
3. Change the Parent dropdown to a different parent or select "None" to make it top-level.
4. Save.

Example hierarchy

Parent label	Child labels
Area	Frontend, Backend, Mobile, Infrastructure
Type	Bug, Feature, Improvement, Chore
Effort	Small, Medium, Large

TIP

Hierarchy is most useful when you have many labels. If your project uses fewer than 10 labels, a flat list is usually simpler to manage.

Apply labels to work items

You can apply one or more labels to any work item:

From the work item detail

1. Open the work item.
2. Click the Labels field in the side panel.
3. Search for and select one or more labels.
4. Labels are applied immediately.

From list or board view

1. Right-click a work item (or click the ... menu).
2. Select Labels.
3. Choose the labels to apply or remove.

Using bulk edit

1. In the work items list, select multiple items using checkboxes.
2. Click Bulk Edit in the toolbar.
3. Under Labels, choose labels to add to all selected items.
4. Click Apply.

Filter by label

Labels are a first-class filter throughout SetGet:

In work items views

1. Open the Filters panel at the top of any work items view.
2. Click Add Filter and select Label.
3. Choose one or more labels to filter by.
4. The view updates to show only items with the selected labels.

Filter operators

Operator	Behavior
is	Show items that have any of the selected labels
is not	Show items that do not have any of the selected labels

In saved views

You can save a label-based filter as a named view for quick access:

1. Apply your label filters.
2. Click Save View and give it a name (e.g., "All Bugs", "Frontend Work").
3. Access the saved view from the sidebar under Views.

In cycles and modules

Label filters work within cycles and modules as well. Use them to see only specific categories of work within a given cycle.

Workspace labels vs. project labels

SetGet supports labels at the project level. Each project has its own independent label set. If you need the same labels across multiple projects, you can:

• Manually create matching labels in each project.
• Use project templates to include your standard labels when creating new projects.

Best practices

• Keep the list manageable — aim for 10-20 labels per project. Too many labels leads to inconsistent tagging.
• Use hierarchy for large label sets — group related labels under parents to keep the settings page and filter dropdowns navigable.
• Establish conventions early — agree on label names, colors, and when to use each label before the team starts working.
• Combine labels with filters — labels are most powerful when used in saved views to create focused work queues (e.g., "My Bugs", "Unresolved UX Issues").
• Review labels periodically — remove labels that nobody uses and consolidate labels that overlap.

Related pages

• Manage Projects — Create and configure projects
• Project Settings — Full settings reference
• Project States — Configure workflow stages
• Views Overview — Create and save filtered views
• Work Items Overview — Apply labels to work items