Workflows
Every project has its own workflow — a set of statuses that tasks move through and rules that govern which transitions are allowed. You can fully customize statuses, define which transitions are valid, and configure task types with per-field rules.Statuses
A status represents the current state of a task. Each status has a name, a color, and a category.Status categories
Every status must be assigned to one of three categories:Configuring statuses
1
Open project settings
Navigate to your project, click Settings in the sidebar, then select Statuses.
2
Add a new status
Click + New Status. Enter a name (e.g., “In Review”, “Blocked”, “Waiting on Customer”).
3
Set the category
Choose TODO, IN_PROGRESS, or DONE. This determines how the status is treated in velocity, burndown, and SLA calculations.
4
Choose a color
Select a color to distinguish the status visually on the board and in lists.
5
Order the statuses
Drag statuses to reorder them. The order here matches the left-to-right order of columns on the board.
Transition rules
By default, tasks can move from any status to any other status. You can restrict this by configuring explicit transition rules.
To configure transitions, open Settings → Transitions and define which statuses can move to which. For each status, select the statuses it is allowed to transition into.
Governed workflows are recommended for regulated or audit-sensitive processes where task progression must follow a defined path.
Task types
Task types categorize different kinds of work. Each type has a name, an icon, and a color. Types control which custom fields are required, optional, or hidden on a task.Inheritance chain
Task types follow a three-level inheritance chain:
Global types are available in every project. Space types extend the global set for a specific Space. Project types extend the space set for a specific project. Each level can add new types but cannot remove or override types from levels above.
Creating a task type
1
Navigate to the correct level
For a global type, go to Admin → Task Types. For a project type, go to Project → Settings → Task Types.
2
Add a new type
Click + New Task Type. Enter a name (e.g., “Incident”, “Change Request”, “Feature”).
3
Set the icon and color
Choose an icon from the icon picker and a color. These appear on task cards and in lists.
4
Configure field rules
Add field rules to control how standard and custom fields behave for this task type (see below).
5
Save
Click Save. The new type is immediately available when creating tasks at the configured level.
Task type field rules
Field rules let you control how each field behaves for a specific task type. For example, a “Bug” type might require a “Steps to Reproduce” custom field, while an “Epic” type might hide the “Story Points” field entirely.
To add a field rule, open a task type’s configuration page and click + Add Field Rule. Select the field, choose the rule type, and save.
Field rules apply to both standard fields (such as Story Points or Due Date) and custom fields configured by your admin. A field marked as Hidden for a task type cannot be set even through the API.
.png?fit=max&auto=format&n=V5LGcGniNC1X_QJO&q=85&s=8c9ba3ce9a0d0045976180c9f669af26)
