Labels

Labels provide flexible categorization for tasks. Unlike task types (which are mutually exclusive), you can apply multiple labels to a single task, enabling cross-cutting concerns like priority, team ownership, or feature areas.

Labels vs Types

Use types for "what it is" and labels for "additional context."

Default Labels

New projects include common labels:

Creating Labels

Project-Level Labels

1. Go to Project Settings > Labels
2. Click "New Label"
3. Enter:

• Name (required)
• Color (pick or enter hex)
• Description (optional)

1. Save

During Task Editing

1. Open task detail
2. Click the labels field
3. Type a new label name
4. Click "Create [name]"

Labels created this way get a random color that you can change later.

Applying Labels

Single Task

1. Open task detail panel
2. Click the Labels field
3. Check labels to apply
4. Click outside to close

Multiple Tasks

1. Select tasks on Kanban (Shift+click)
2. Open bulk actions menu
3. Choose "Add Labels" or "Remove Labels"
4. Select labels to modify

Quick Add

On the Kanban board, hover over a task card and press L to open the label picker.

Label Naming Conventions

Namespaced Labels

Use prefixes for organized labels:

priority:high
priority:medium
priority:low

team:frontend
team:backend
team:design

status:blocked
status:needs-review
status:in-testing

Emoji Labels

Some teams use emoji for visual scanning:

🔥 urgent
🐛 has-bugs
🎨 needs-design
⏰ deadline-soon

Keep It Simple

• Use lowercase
• Use hyphens for spaces
• Keep names short
• Be consistent across projects

Filtering by Labels

Kanban Board Filter

1. Click the filter icon
2. Select "Labels"
3. Choose labels to include/exclude
4. Toggle "Match All" or "Match Any"

Quick Search

Use ~ prefix for label search:

~blocked
~priority:high api

Saved Views

Create views for common label filters:

• "Blocked Items" - all blocked tasks
• "Review Queue" - needs-review tasks
• "Client Issues" - customer-reported items

Label Colors

Color Categories

Choose colors with meaning:

Color Picker

The label editor provides:

• Preset color palette
• Hex input for custom colors
• Color preview

Contrast

Ensure text remains readable on colored backgrounds. GitScrum automatically adjusts text color based on background.

Managing Labels

Editing Labels

1. Go to Project Settings > Labels
2. Click a label to edit
3. Modify name, color, or description
4. Save

Changes apply to all tasks with that label.

Merging Labels

To consolidate duplicate labels:

1. Go to Project Settings > Labels
2. Click the merge icon on a label
3. Select the label to merge into
4. Confirm

Tasks move to the target label; source label is deleted.

Deleting Labels

1. Go to Project Settings > Labels
2. Click delete on a label
3. Choose what to do with tagged tasks:

• Remove label from tasks
• Replace with another label

1. Confirm

Archiving Labels

For temporary labels you might need again:

1. Mark as archived instead of deleting
2. Archived labels don't appear in pickers
3. Unarchive anytime to restore

Label Scopes

Project Labels

Default scope. Labels are specific to one project.

Workspace Labels

Agency Owners can create workspace-wide labels:

1. Go to Workspace Settings > Labels
2. Create labels here
3. Available in all projects

Useful for:

• Cross-project priorities
• Organization-wide status labels
• Shared team labels

Automation with Labels

Label Triggers

Set up automations based on labels:

• When blocked added → notify manager
• When priority:high added → move to top of column
• When needs-review removed → move to "Done"

Integration Labels

Some integrations use labels for sync:

• github-pr for linked pull requests
• external-sync for third-party connections

Reporting

Label Distribution

View label usage across tasks:

1. Open Project Reports
2. Select "Label Distribution"
3. See which labels are most common

Time by Label

Track time spent on labeled work:

1. Open Time Reports
2. Filter by label
3. See hours per label category

Burndown by Label

In sprint analytics, toggle label visibility to see progress on specific concerns.

Best Practices

Start Small

Begin with 5-10 essential labels. Add more as needs emerge.

Document Usage

Create a wiki page explaining:

• What each label means
• When to apply/remove
• Who manages labels

Regular Cleanup

Monthly review:

• Delete unused labels
• Merge duplicates
• Update descriptions

Limit Required Labels

Don't force labels on every task. They're most valuable when applied intentionally.

Pro Tips

• Keyboard shortcut: Press L on a selected task to open label picker

• Color coding: Use the same color for related labels (all priority labels in red shades)

• Temporary labels: Create sprint-specific labels for tracking, delete after sprint

• Negation filtering: Filter for tasks NOT having a label to find uncategorized work

How to Report a Problem or Request a Feature

If you need additional label features or encounter issues, submit feedback through GitScrum Studio. In the Sidebar, click on Support Tickets and open a ticket.