Feature Requests

Please search first before posting to help others find and vote for your idea!
Support rich text / ClickUp editor formatting in Docs API and MCP
When reading or writing Doc pages via the API or MCP server, only text/md (Markdown) and text/plain are supported as content formats. This means that any rich formatting applied in the ClickUp editor — such as colored text, callout blocks, banners, column layouts, and other editor-specific elements — is lost when a page is written back via the API or MCP. This creates a real problem for AI assistant workflows (e.g. using the official MCP server with Claude or other LLMs): if a Doc page has been carefully formatted in the ClickUp editor, any AI-assisted update to that page will strip all of that formatting, since the only write path available is Markdown. What I'd like: Either (or all) of the following: * idea 1: A richer content format option (e.g. text/html or a ClickUp-native rich text AST) for both reading and writing Doc pages, so that formatting round-trips cleanly. * idea 2: A read-only rich format so that the original formatting can be fetched and preserved when writing back — even if writes remain Markdown-only. * idea 3: An API / MCP tool to insert in a doc at a certain position, so we can just update selected part without rewriting the whole doc (added value: likely to save tokens) Use case: Using the ClickUp MCP server with an AI assistant to append or update content in Doc pages that were formatted in the ClickUp editor. Currently, doing so risks destroying the existing visual structure of the document.
5
·
Docs
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.
19
·
Task types
·
building now
Load More