Choose Workflow Schemes and Priority Sets
Understand how workflow schemes and priority sets control a project’s task behavior.
These project settings reuse workspace configuration. Choose an existing scheme and set during project creation, or keep the defaults supplied by the selected project template and workspace.
Key terms
Workflow Schemes
A workflow scheme decides which workflow each task type uses in the project. Its default workflow applies unless a task type has a specific override. The resolved workflow controls the statuses a task can use and the transitions available as work moves through the board.
- Choose Template default to use the workflow scheme selected by the project template.
- Create and edit reusable schemes in Workspace settings → Workflow assignments.
- Review the impact before changing a scheme used by active projects because one workspace scheme can serve multiple projects.
- After creation, view the effective task-type mappings in Project settings → Task types & workflow.
Priority Sets
A priority set determines which priority values are available to the project, their display order, and the default selected for new tasks. It classifies urgency; it does not change a task’s workflow or status.
- Choose Workspace default to inherit the workspace’s default priority set.
- Create priorities and manage reusable sets in Workspace settings → Priorities & sets.
- Change the set assigned to an existing project in Project settings → Priorities & sets.
- Keep sets small and consistent so users can distinguish the urgency levels reliably.
What To Choose During Project Creation
Keep the defaults when the template and workspace already match the team’s process. Select an explicit workflow scheme or priority set only when this project needs a known workspace configuration. The preview below each selector shows what will be assigned before the project is created.
Best practices
- Reuse schemes and sets across projects that follow the same operating model.
- Use clear names that describe the process or urgency model rather than a single project.
- Review shared configuration changes with every project that uses them.
Common mistakes
- Treating a workflow scheme as a list of board columns instead of task-type workflow assignments.
- Creating a separate priority set when the workspace default already meets the project’s needs.
- Changing shared configuration without checking its effect on existing projects.