Custom Status Creation

Overview

Custom statuses support delivery workflows that vary by Organization.

They standardize reporting and approvals when defaults do not fit.

Key Concepts

• Status type: workflow definition for an item type
• Status: state label within a workflow
• Default status: starting state used for new items

How It’s Used

Use custom statuses when governance needs differ across Projects.

Keep workflows stable to protect reporting continuity.

Benefits

• Consistent execution signals
• Cleaner governance reviews
• Better alignment across delivery teams

Setup Steps

1

Open status configuration

1. Navigate to Project Settings.
2. Open Statuses (or equivalent area).

2

Create or edit a status type

1. Select an item type, such as Tasks or Requirements.
2. Select Create status type (or Edit).
3. Name the status type with intent.

3

Add statuses and order

1. Add the required statuses.
2. Order statuses in the expected progression.
3. Set a default starting status.

4

Validate reporting impact

1. Confirm Save Views and dashboards reflect the new statuses.
2. Update team guidance for meaning changes.

Best Practices

• Keep workflows minimal.
• Use the same status meanings across Projects when possible.
• Avoid frequent changes after delivery begins.

Summary

Custom statuses should support governance and reporting.

They should not be used for one-off exceptions.