Feature Requests

Please search first before posting to help others find and vote for your idea!
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!
1
·
Email
Merge Fields (a la Mail Merge) for Auto-Populating Custom Fields Data
Wouldn’t it be amazing if.... we could use merge fields to auto-populate data from custom fields? For example, auto-populating data in task descriptions or, in particular, documents….? Let’s say that you have a workflow that has you referencing custom field data for external parties every. single. time. you run said workflow. For example, you might track key metrics in custom fields that you need to summarize for your client, or for a group of people outside of your team, or that you need to update your client or group on with regularity. And every time you do that, you have to transpose said data manually. If it’s just a single client that you are sharing data with, creating a guest account for that person makes sense. However, to use my own case as an example, I am regularly sharing data from custom fields with a different group of people for every project, so it’s just not feasible to create guest accounts for every single person who needs access to this data. So what if, instead of manually transposing data every time, you could.... Create a template document in a Doc view; Use merge fields to reference custom fields in your template document; Link the specific task, whose custom field data you want populated, in said document; and Regain HOURS of lost productivity every year from the time no longer lost to manual data transfer. The only thing I’ve seen like this from a competitor is Airtable’s Page Designer block, which uses merge fields to reference record data (which would be the equivalent of a ClickUp task). I wouldn’t say that ClickUp should have a full blown page designer, but even just the ability to use merge fields with documents in their current state would be AMAZING. And in fact, I actually prefer ClickUp's ability to create a public link to a document, where the custom field data would update automatically, to Airtable's Page Designer where you have to export a single-point-in-time document as a PDF.
36
·
Email
Load More