Project Management – Process: Work Item Types & Status Mapping

4 min. readlast update: 12.30.2025

Process: Work Item Types & Status Mapping

Module

Control Center → Project Management

The Work Item Types & Status Mapping configuration defines how work is structured, tracked, and progressed within projects that use a specific Project Process.

This configuration controls:

  • Which work item types are available
  • How work items are organized hierarchically
  • Which statuses are allowed for each work item type
  • How execution, planning, and reporting behave across projects

It is one of the most critical configurations for ensuring consistency and governance in project delivery.


Access Path

Control Center → Project Management → Process → Work Item Types


1. Purpose of Work Item Type Configuration

Work Item Type configuration allows organizations to:

  • Standardize how work is broken down and executed
  • Align work structures with delivery methodologies
  • Control lifecycle progression via status rules
  • Ensure reporting consistency across projects
  • Prevent invalid status transitions for specific work item types

Each Project Process can define its own combination of work item types and allowed statuses.


2. What Is a Work Item Type?

A Work Item Type defines the role a work item plays in a project.

Typical examples include:

  • Timeline
  • Phase
  • Task
  • Issue
  • Epic
  • Story
  • Bug
  • Milestone

The actual list of available types depends on configuration elsewhere in the Control Center.


3. Work Item Types Tab Overview

The Work Item Types tab displays a list of work item types associated with the selected process.

For each work item type, administrators can define:

  • Whether the type is enabled for the process
  • Which statuses are allowed
  • How work progresses within that type

4. Mapping Statuses to Work Item Types

Each work item type must be mapped to one or more allowed statuses.

4.1 Status Mapping Rules

Rule Description
Allowed Statuses Only mapped statuses can be selected when updating a work item of that type.
Status Reuse The same status may be reused across multiple work item types.
Type-Specific Control Each work item type can have a different lifecycle, even within the same project.

5. Hierarchy and Execution Behavior

Work item types influence how work behaves in planning and execution:

  • Parent work items (e.g., Timeline, Phase) often aggregate:

    • Dates

    • Effort

    • Cost

  • Child work items (e.g., Tasks, Stories) represent executable work

  • Status changes may cascade or roll up depending on configuration

This hierarchy ensures structured planning and accurate reporting.


6. Methodology Alignment

Waterfall

  • Strong hierarchy (Timeline → Phase → Task)
  • Status progression tightly controlled
  • Emphasis on dependencies and completion order

Agile

  • Flat structure (Epic → Story → Task)
  • Flexible status progression
  • Focus on board execution and iteration

Hybrid

  • Hierarchical planning with Agile execution
  • Combination of strict and flexible status rules

Each Project Process can tailor work item types to match its methodology.


7. Impact on Project Features

Work Item Type configuration directly affects:

  • Board columns and workflow
  • Timeline and Gantt views
  • Progress calculation
  • Summary & Analytics charts
  • Reporting and KPIs
  • Validation rules during execution

Incorrect mappings can lead to inconsistent reporting or blocked execution flows.


8. Governance & Change Management

Important considerations:

  • Changes affect all projects using the process
  • Removing a work item type may impact existing data
  • Status changes should be aligned with governance rules
  • Tenant-wide processes should be modified cautiously

Best practice is to review and validate changes in a controlled environment.


9. Recommendations

  • Keep the number of work item types limited and meaningful
  • Avoid overly complex status lifecycles
  • Align work item types with real execution practices
  • Ensure parent work items cannot be closed prematurely
  • Review status mappings whenever processes evolve

10. Summary

The Work Item Types & Status Mapping configuration defines the structural and behavioral foundation of project execution.

By carefully configuring work item types and their allowed statuses, organizations ensure:

  • Predictable execution
  • Accurate reporting
  • Strong governance
  • Methodology alignment

This configuration completes the definition of a Project Process.


Related Articles

Project Management – Process (Overview)
Project Management – Process: Core Configuration
Project Management – Process: Features
Project Management – Process: Summary & Analytics
Project Management – Status: Work Items
Project Management – Status: Milestones
Project Management – Project Execution Overview


 

Was this article helpful?