Feature Requests

Please search first before posting to help others find and vote for your idea!
Restrict Task Types by List and Location
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.
16
·
Task types
·
building now
Feature Request: EMAIL THREAD RECOGNITION FOR EMAIL-TO-TASK (for help desk support tickets)
Enable ClickUp's email-to-task feature to recognize email threads and add reply emails to the existing task instead of creating duplicate tasks. Current Behavior: When using ClickUp's email-to-task functionality: Initial email to List email address creates Task A User replies to client from within ClickUp task Client replies to that email thread ClickUp creates NEW Task B instead of adding the reply to Task A Requested Behavior: When a client replies to an email thread that originated from a ClickUp task: ClickUp should recognize the email thread/conversation ID Add the reply as a comment/update to the original task Maintain the full email conversation within one task Optionally notify assigned users of the new reply Business Use Case: Many teams want to use ClickUp as a customer support help desk system with a single support email address (e.g., support@company.com ). For this to work effectively, email conversations need to be threaded within the same task, not scattered across multiple tasks. Current Workaround Limitations: Manual task merging (time-consuming, error-prone) Losing conversation history across multiple tasks Poor customer experience tracking Forces teams to purchase separate help desk software (Teamwork, Front, Help Scout, Zendesk) just for email threading Impact: This feature would allow ClickUp to serve as a true help desk ticketing system, eliminating the need for third-party integrations and making ClickUp more competitive with dedicated support platforms. Technical Requirements: Parse email headers to identify thread/conversation IDs Match incoming emails to existing tasks by conversation ID Add subsequent emails as task comments with email metadata Maintain ability to reply from task and continue thread Priority: High - This is a major limitation preventing ClickUp from being used as a complete support solution. Thank you!
5
·
Email
Load More