Restrict Task Types by List and Location
planned
Danielle Little
Currently, when we create a task type, it becomes available across the entire workspace. This creates issues for standardization, as we want to enforce the use of specific task types within certain lists and even based on location.
We’d like the ability to restrict task types to a list or location, so team members only see the relevant options. For example, in some cases, we only want three task types available within a given list.
This functionality will help us:
*Enforce consistency in how tasks are categorized.
*Limit confusion by only presenting relevant task types.
*Better leverage the beta functionality of fields tied to task types.
IMPACT:
Without this, team members can select incorrect task types, leading to data inconsistency and reduced effectiveness of field-based reporting and automation.
REQUEST:
*Ability to configure which task types are available per list, space, and/or entire workspace. Include the ability to manage ClickUp-created task types, such as Task, Milestone, Meeting Note, Key Result, Person, etc.)
--By Location (Department/Team/Region): For example, the Sales – Europe list may only need three task types (“Lead,” “Demo Scheduled,” and “Contract Sent”), while Sales – US might require a different set. Restricting by location would keep task types relevant for each group.
--Space: If an organization manages multiple workspaces (e.g., Operations vs. IT), admins could enforce different task type sets per workspace. This would prevent irrelevant task types from appearing in the wrong context (e.g., IT-specific types showing up in Sales).
--Workspace: We may want to make certain task lists available across the workspace still.
*Add to the space configuration/creation to set the task types available for each, in case there are no task types available at the workspace level.
Log In
Raina Ahuja
Danielle Little Henrik Hjort David J Geiger Thank you for your feedback and use cases! Excited to share that we're currently scoping this effort.
Quick question - if a task is moved to a location where its type does not exist, what would you expect to happen?
- Keep the task's type and add it to the list of types set to that location
- Force a remap to any of the types set to that location
- Auto-convert to the default type in that location
- Warn and block the move entirely
- Other (pls share in the comments!)
Raina Ahuja
marked this post as
planned
Rodrigo Carballo
Raina Ahuja Hello. I would expect ClickUp to treat that move as it does when importing or moving tasks. I would expect to be prompted to remap my task type or create a new allowed task type in the list I’m moving the tasks to. It’s intuitive and very straight forward.
Danielle Little
Rodrigo Carballo I agree with the prompt to remap.
Henrik Hjort
The more I use task type the more I need this.
David J Geiger
This is so clear and detailed! I agree with this 100%