Workflow Customization & Status Transition Restrictions
Denys Moskalyk
I’d like to request an enhancement to ClickUp’s workflow management that would allow more granular control over status transitions and the visibility of statuses within different lists and folders, similar to how it is organized in Jira.
Key Requests:
- Restrict Status Transitions
• Ability to define which statuses a task can transition to from its current state.
• Example:
• From “In Development” → Only to “Ready for Testing” or “Code Review”
• From “Ready for Testing” → Only to “Tested” or “Redo”
• From “Tested” → Only to “Done”
• Prevent users from skipping required workflow steps by enforcing structured transitions.
- Folder-Based Workflow Rules
• Allow setting workflow rules per folder (not just per space or list), so different projects or issue types can have specific process flows.
• Enable different transition rules for different lists under the same folder, ensuring tailored workflows for specific project needs.
- Status Visibility Customization
• Ability to show/hide specific statuses per folder to ensure that only relevant statuses are available for selection in a given project.
• Example: A development project might need statuses like “In Development,” “Code Review,” “Tested,” while a design project might require “In Progress,” “Review,” “Approved.”
• This would prevent clutter from a long, mixed list of statuses and help teams work more efficiently by only showing relevant options.
Why This is Important
1. Improves Process Compliance – Prevents team members from accidentally skipping essential workflow steps.
2. Enhances Process Automation – Reduces manual errors by enforcing structured transitions.
3. Better User Experience – Customizable status visibility ensures teams only interact with relevant statuses, avoiding unnecessary choices.
4. Better Alignment with Industry Standards – Many teams using Jira benefit from similar restrictions to maintain workflow discipline.
Log In