Work Items Status Mapping

Status Mapping Guide

Overview

This guide explains how to map your statuses.
You’ll define:

  • Workflow order (status order)
  • Status type (status kind)
  • Inception and Delivery points (where work starts and ends)

These mappings power key analytics such as throughput, cycle time, and Estimated vs. Executed metrics.

How to Access the Mapping UI

  1. Go to Productivity Tools → Manage Boards
  2. Select at least one board
  3. For each Issue Type:
    • Reorder statuses (drag and drop)
    • Set Status Kind for each status
    • Toggle Inception and Delivery where appropriate
  4. Click Continue → Save

Status Order

Arrange statuses in the order your work typically flows.
The first status should represent the earliest stage (e.g., Backlog or To Do).
Orders are automatically assigned in increments of 10 (0, 10, 20, …).

Example Order

OrderStatus
0Backlog
10To Do
20In Progress
30In Review
40QA
50Done

Status Kind

Each status must be assigned one of the four kinds:

KindDescriptionExamples
BacklogPlanning or intake stages before active work beginsBacklog, Idea, Selected for Development, To Do
ActiveExecution stages where hands-on work occursIn Progress, Coding, Development, Analysis, QA (hands-on)
WaitingPaused or blocked states; waiting for review or approvalBlocked, On Hold, In Review, Ready for QA, Awaiting Approval
DoneFinal completion; work is finishedDone, Closed, Resolved, Released, Deployed

Tips

  • Use Active (1) when someone is doing hands-on work.
  • Use Waiting (2) when work is paused or pending others.
  • Use Done (3) only when work is fully complete.

Inception (Work Start Flag)

Set Inception = ON only on the first status where real work begins.

Typical Choices: In Progress, Analysis, Development
Do NOT set on Backlog or To Do.

If your workflow includes a Discovery or Analysis stage where effort is invested, you can mark Inception there.
→ Usually only one status should have Inception = ON.

Delivery (Completion/Release Flag)

Set Delivery = ON only on the status that represents actual delivery or release of value.

Typical Choices: Done, Released, Deployed, Closed
Do NOT set on intermediate states like “Ready for Release.”

If you have multiple “Done-like” statuses, choose the one that truly means delivery to users or customers.

Common Examples

Simple Flow

StatusKindInceptionDelivery
Backlog0OFFOFF
To Do0OFFOFF
In Progress1ONOFF
In Review2OFFOFF
QA1 or 2OFFOFF
Done3OFFON

With Release Gate

StatusKindInceptionDelivery
Backlog0OFFOFF
To Do0OFFOFF
In Progress1ONOFF
QA1OFFOFF
Ready for Release2OFFOFF
Released3OFFON

With Analysis / Discovery

StatusKindInceptionDelivery
Backlog0OFFOFF
Analysis1ONOFF
In Progress1OFFOFF
In Review2OFFOFF
Done3OFFON

With Blocked

  • Blocked → Kind = 2 (Waiting), Inception = OFF, Delivery = OFF

With Canceled / Rejected

If retained for recordkeeping:

  • Use Done (3) with Delivery = OFF (not released), or
  • Waiting (2) if it’s a terminal “not delivered” outcome.
    Be consistent across all boards.

Quality Checklist

✅ Status order reflects real workflow from earliest to latest
✅ Only one “Inception” status (first work stage)
✅ Only one “Delivery” status (true release point)
✅ “Active” vs “Waiting” applied consistently
✅ “Done” reserved for final completion
✅ Edge cases (Blocked, Canceled, Ready for X) categorized consistently

FAQs

Q: Should QA be Active (1) or Waiting (2)?
A: If testers are actively testing → Active (1).
If it’s waiting in queue → Waiting (2).

Q: We have multiple “Done-like” statuses. Which gets Delivery?
A: Only the one representing true release to users.

Q: Can I set multiple Inception statuses?
A: Avoid this; pick the earliest stage where effort begins.

Q: Do I need to manually set numeric orders?
A: No — drag-and-drop assigns them automatically.

Saving Your Mapping

Once you’ve set:

  • Order
  • Kind
  • Inception
  • Delivery

Click Save to confirm changes.
You can revisit and adjust mappings anytime as your process evolves.

💡 Need help?
Our Customer Success team can assist your organization in reviewing or optimizing mappings.
Contact us at support@leanmote.com.

Powered By EazyDocs