Task Types

Task types categorize work items into logical groups. Each type has its own color and icon, making it easy to visually distinguish bugs from features, documentation from technical debt.

Default Task Types

GitScrum provides standard types out of the box:

Why Task Types Matter

Visual Organization

On the Kanban board, task type colors create instant recognition:

• Red cards need investigation (bugs)
• Green cards add value (features)
• Orange cards reduce future friction (tech debt)

Filtering

Filter your board by type to focus on:

• Bug triage sessions (show only bugs)
• Feature planning (show only features)
• Documentation sprints (show only docs)

Reporting

Track work distribution:

• How much time goes to bugs vs features?
• Is technical debt increasing or decreasing?
• Are documentation tasks being prioritized?

Sprint Planning

Balance sprint composition:

• Don't fill sprints with only bugs
• Include technical debt regularly
• Ensure documentation stays current

Assigning Task Types

During Task Creation

1. Open the Create Task modal
2. Click the Type dropdown
3. Select the appropriate type

If no type is selected, tasks default to "Task" type.

On Existing Tasks

1. Open the task detail panel
2. Click the type badge
3. Select the new type

Type changes are instant and reflected immediately on the board.

Bulk Updates

1. Select multiple tasks (hold Shift + click)
2. Use the bulk actions menu
3. Choose "Change Type"
4. Select the target type

Custom Task Types

Managers and Agency Owners can create custom types for their projects.

Creating a Custom Type

1. Go to Project Settings
2. Select the Types tab
3. Click "Add Type"
4. Configure:

• Name
• Color
• Icon (optional)
• Description (optional)

1. Save

Editing Types

Click any existing type to modify its properties. Changes apply to all existing tasks of that type.

Deleting Types

1. Click the delete icon on a type
2. Choose a replacement type for existing tasks
3. Confirm deletion

Tasks are never deleted—they're reassigned to the replacement type.

Type Workflows

Some teams create types specific to their workflow:

Development Team

Design Team

Marketing Team

Best Practices

Keep Types Focused

• 5-8 types is usually sufficient
• Each type should be clearly distinct
• Avoid overlapping definitions

Document Your Types

Create a wiki page explaining:

• When to use each type
• How types affect workflows
• Examples for edge cases

Review Regularly

Periodically audit type usage:

• Are all types being used?
• Do you need new types?
• Should any be consolidated?

Consistency Across Projects

Consider using the same types workspace-wide for consistent reporting.

Type Icons

Available icons include:

• Bug (beetle)
• Feature (lightbulb)
• Task (checkbox)
• Documentation (book)
• Question (help circle)
• Warning (alert)
• Star (important)
• Clock (time-sensitive)

Filtering by Type

Quick Filter

Click the filter icon on the Kanban board:

1. Select "Type" filter
2. Check desired types
3. Board updates immediately

Saved Views

Create saved views for common filters:

• "Bugs Only" view for triage
• "Features" view for roadmap planning
• "Tech Debt" view for cleanup sprints

Search

Use type filter in Quick Search:

type:bug login error

Finds bugs containing "login error".

Type Colors

Choose colors that create meaning:

• Red: Urgent, problems, bugs
• Green: New value, features
• Blue: Improvements, process
• Orange: Attention needed, debt
• Purple: Creative, documentation
• Gray: Neutral, general tasks

Avoid using too many similar colors—distinctiveness matters more than aesthetics.

Reporting by Type

Time Distribution

View time spent per type:

1. Go to Project Reports
2. Select "Time by Type" report
3. Choose date range

Velocity by Type

See completion trends:

1. Open Sprint Analytics
2. Filter by type
3. Compare across sprints

Burndown by Type

Track progress on specific work:

1. Open sprint burndown
2. Toggle type visibility
3. See contribution by type

How to Report a Problem or Request a Feature

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