Feature Requests

I'd like to insert a date directly into text by picking it from a calendar, instead of typing it by hand. Proposal: a /date slash command (and/or @date) that opens a calendar picker and inserts the chosen date as a date element in task descriptions, comments, Docs and Chat. Ideally with quick options like Today and Tomorrow, and a format that follows my profile's date settings. Current limitation: /due, /sd and /today only set the task's Due/Start date fields. There is no way to put a date inside the text itself, so I have to type dates manually, which is slow and leads to inconsistent formats. Reference: Microsoft Loop's @date component does exactly this and works great. I moved from Loop to ClickUp and this is the one thing I miss daily. Use cases: meeting notes, lesson plans, status updates, deadlines mentioned inside a description. Related requests: "inline date picker in Docs table cells" and "Slash command to paste Today's date as plain text".

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.

Problem Tables in Docs have no real header row. The best you can do is make the first row bold with a grey background, and it scrolls away like any other row. With long, wide tables (evidence matrices, test logs, cause/effect tables) you lose track of which column is which after a few rows, so you keep scrolling back up or have to split one table into many. Requested feature Mark rows as header rows: a "Set as header row" option in the row menu, for one or more top rows. Sticky on scroll: header rows stay pinned at the top of the viewport while you scroll through that table, and release when the table ends. Optional header column: pin the first column the same way for wide tables that scroll horizontally. Keep the semantics everywhere: header rows survive copy/paste, export (PDF, Markdown, HTML as <th> ) and import from Excel / Google Sheets when the source has a header row. Why it matters * Readability: engineering, QA and research teams use Docs tables as living reports. A 15+ row matrix with 4 or more text-heavy columns is hard to read without a fixed header. * Consistency: Table view already has fixed headers and pinned columns, so users expect the same in Docs. * Fewer workarounds: today people split one logical table into many small ones, which hurts structure and makes it harder to keep the data consistent. Acceptance criteria * Toggle header rows per table from the row options menu. * Header stays visible while any part of the table body is on screen. * Works in Docs, wikis and task descriptions, in light and dark mode. * Exported files carry the header marking.

One thing that is extremely powerful in google docs is the "Suggest Changes" mode similar to the track changes mode in Office. I think it would be very valuable to add such a mode to clickup docs to further push the collaborative nature of CU docs.

A Visual hierarchy aid for documents / wiki creation. Allowing use of drag and drop relocation. Hierarchy base points could be changed via selection (space, task, folder) - other documents placed under that would take the root location.

I have noticed that when I view a Doc on the mobile app, Columns stay horizontal instead of auto-stacking in some way. Because they stay in a horizontal row, the columns become so squished together the text is unreadable. It would be great if the columns would auto-stack when the viewport got too small or when on mobile, so that they can be actually readable. A "Table" will sort of fix this problem, but on mobile, you have to swipe to see the entire contents, which makes sense for showing multiple rows, but unnecessary with a column layout.

Tables should be the full width of a Doc with all of the columns defaulting to equal width and resizable while maintaining full width. Tables should not be fixed width! Or just add a simple button like Notion "Fit Table to Page Width" which then automatically resizes the table and columns. Right now in ClickUp I have to manually resize each column and it never is quite full width or symmetrical, and doesn't resize from Default page width to Full page width. You also can never have two columns exactly the same width. Moving from the simple, fast, and elegant tables in Confluence over to ClickUp has been a shocker. All of my migrated tables look horrible in ClickUp Docs. If you want to see how to build tables right, look at Confluence. It doesn't get any better. And header rows would be so simple for you guys to add.

It is currently not possible to copy and paste from tables (in Docs) into other areas of ClickUp, or other applications. This is a major limiting factor in using Tables in Docs. We really need the ability to copy and paste from Doc Tables to anywhere in ClickUp or other applications.

Please add the ability to export docs to MS Word. This is essential, otherwise Docs are useless for me. This is because clients often require documents in their own Word templates. For example, In Jira, I can generate a table from issues (lists) that appear in a Confluence document. That Confluence document can then be seamlessly exported to Word, which can be tweaked to fit the client's template. Exporting a ClickUp document in PDF format does not allow me to do this, so I continue to use Jira/Confluence. If ClickUp were to export docs to Word then I may switch my process.

Need a better way to export doc's so they can be used/opened/converted into MS Doc/Google Doc's without a huge lift in formatting. Currently leveraging doc's for things like SOP's is difficult because in the event it needs to move outside of ClickUp, there is no export to doc function currently. PDF/Markdown are not good enough to accomplish this, you lose formatting and the structure. For Doc's to be used more heavily by our team, there needs to be a form of continuity in place, where creating it in ClickUp gives us assurance that we can move it elsewhere with formatting intact.