Feature Requests

We use clickup as a CRM. With this we assign tasks to a customer "task" and a company "task" in our support list. We have 1000s of customers and many of them with the same / similar name. It would be a GODSEND if we could, when assigning a relationship from search, see ALL the tasks rollup fields in the list so that we have more context on knowing which task is which. Currently we have to click on a task and hope it's the right one to see the rollup fields and if it's not the right one, we have to click the X and try again. If we could see the roll up fields in the search drop down, we would be able to know the task the first time. This has been requested many times before: https://feedback.clickup.com/feature-requests/p/show-tags-in-rollup-fields-in-relationships https://feedback.clickup.com/feature-requests/p/search-or-show-at-least-rollup-fields-when-adding-a-relationship https://feedback.clickup.com/feature-requests/p/allow-custom-fields-when-choosing-the-relationship-rollup-option-for-any-task-in are the first 3 of this request I've found.

Summary We use AI assistants connected to ClickUp to automate our sprint metrics, through the public API and the official ClickUp MCP server. These tools can read tasks, lists and comments. They cannot read Sprint Reporting (Sprint Task Report, and the Burndown/Burnup and Velocity reports), because that data is not exposed through the API or the MCP. We ask that it be made available to AI integrations. Current behavior The MCP server and the public API have no endpoint or tool for sprint reports. An AI assistant only sees the current state of each task. It cannot see the committed snapshot taken at sprint confirmation or the Added/Removed/Completed/Remaining breakdown that ClickUp already calculates and shows on screen. Rebuilding this data from task history gives wrong results: moving a task between lists does not update date_updated, and closed sprints cannot be recovered at all. ClickUp Brain also cannot answer questions such as "how many points were added to Sprint 27 after confirmation?" Why it matters Our product team runs an automated routine with an AI assistant that collects sprint metrics (committed vs. completed, scope added mid-sprint, carry-over) and publishes them for leadership. Sprint Reporting is the only reliable source for these numbers. Without access, the routine depends on someone copying values from the screen by hand. Requested improvement Public API endpoint(s) that return the Sprint Task Report for a given sprint: per-sprint totals, plus a per-task list with ID, name, assignee, points, status, category (Committed / Added / Removed / Completed / Remaining / After sprint close) and the date the task entered or left the sprint. This must include the committed snapshot at confirmation time. The same data exposed as tools in the official ClickUp MCP server, so assistants such as Claude, ChatGPT and Copilot can query it with the user's permissions. Velocity and Burndown/Burnup data through the same endpoints, covering several sprints at once. (Nice to have) ClickUp Brain able to answer questions using Sprint Reporting data. Acceptance criteria Given a confirmed sprint, when an AI assistant calls the API or MCP for that sprint's report, then it receives every task with its category, and the totals match the cards shown in Sprint Reporting. Given a sprint that is already closed, the response still returns the committed snapshot as it was at confirmation. The response uses the effort measure set for the report (sprint points, time estimate or task count). Access follows the same permissions as the user or token that authenticated the request. Environment Sprints ClickApp, Sprint Reporting → Sprint Task Report. Effort measure: Sprint Points. Sprint length: 2 weeks. Clients: public API v2 and the ClickUp MCP server.

Summary The Sprint Reporting area ("Sprint Task Report") shows useful sprint data: Committed, Added, Removed, Completed, Remaining, and tasks after sprint close. However, there is no way to export it. We need to get this data out of ClickUp to track team metrics over time. Current behavior The report only shows totals (e.g., Sprint 27, 05/10/26–19/10/26: Committed 160 pts, Added 55 pts, Removed 6 pts, Completed 44 pts, Remaining 165 pts) and a task breakdown by category. The "…" menu has no option for CSV/Excel/PDF export, copy, or scheduled sending. The public API does not expose this data either. In particular, it does not give the committed snapshot taken at sprint confirmation (e.g., "Confirmed: Oct 5 at 13:00 UTC-03") or which tasks were added or removed after that point. Rebuilding this from task history is unreliable: moving tasks between lists does not update date_updated, and for older sprints the data cannot be recovered at all. Why it matters Our product team tracks planning predictability (committed vs. completed, scope added mid-sprint) across sprints. Today we have to copy numbers by hand from the screen, sprint by sprint. This is slow and error-prone, and it is impossible for sprints that are already closed if nobody wrote the numbers down. Requested improvement Export button in the Sprint Task Report (CSV and/or XLSX). It should include each task's ID, name, assignee, points, status, the category it belongs to (Committed / Added / Removed / Completed / Remaining / After sprint close), and the date it entered or left the sprint. Summary export with the totals per sprint, so we can export several sprints at once and compare them. API endpoint that returns the same report data, including the committed snapshot at confirmation time, so we can automate our metrics. (Nice to have) Scheduled export by email when a sprint closes. Acceptance criteria Given a confirmed sprint, when I click Export in the Sprint Task Report, then I get a file with every task and its category, and the totals in the file match the cards on screen. Given a sprint that is already closed, the export still returns the committed snapshot as it was at confirmation. The export follows the effort measure set for the report (sprint points, time estimate, or task count). Environment Sprints ClickApp, Sprint Reporting → Sprint Task Report. Effort measure: Sprint Points. Non-working days: Saturday and Sunday. Sprint length: 2 weeks.

Allow a single task or subtask to have multiple nonconsecutive work dates or date ranges, displayed as separate Timeline blocks with gaps, without creating additional tasks. Our projects involve irregular delivery days across multiple weeks, and continuous bars overstate the work involved while splitting tasks adds unnecessary admin. Many thanks!

We want to replace Microsoft Teams with ClickUp Chat, but we need to be able to add people to existing group conversations with access to the full conversation history. Starting a new group chat does not meet this need because it separates new participants from the existing context. Please confirm whether this is possible and, if so, how; if not, please register this as a feature request and let us know whether it is on your roadmap. We would also appreciate a way to submit support requests directly from ClickUp Brain without having to leave the conversation and manually copy the details.

Please add an option to hide ClickUp branding, including the top header, from publicly shared Artifacts: when using them embedded on an organization’s website or sharing them with clients and partners, the extra branding makes the result feel less professional and distracts from our own identity. A “Hide ClickUp branding” toggle, similar to Forms, would be ideal, potentially included in the Business plan or above. The existing request appears completed, but public links still show the branded header, so please extend this option to the entire public page, not just the “By ClickUp Brain” badge. https://feedback.clickup.com/feature-requests/p/remove-clickup-branding-from-artifact

When I share a public Doc or view link on WhatsApp, Instagram or email, the preview always shows the generic "ClickUp Docs" image. As a design studio sharing course material and client deliverables, I'd love to set a custom thumbnail, title and description per Doc/page/view (e.g. using the Doc cover image and title by default). This would make shared links look professional and on-brand.

Problem More and more of our work runs through terminal agents and wrappers: Claude Code, Codex CLI, Cursor, pi and custom orchestrators. Brain is the one assistant that actually knows our company, with workspace context, installed skills, memory, connected apps and permissions. But it only exists inside the ClickUp UI and Brain MAX. So we either keep switching between tools, or we rebuild that context badly in other agents. The ClickUp MCP server doesn't solve this. It gives another model raw access to tasks and docs. It doesn't give us Brain itself: its skills, memory, Super Agents, connected-app search, or its judgment about our workspace. Request A first-party Brain CLI and agent endpoint: Auth: brain login using OAuth or a device-code flow tied to my ClickUp account. Tokens are scoped to my existing permissions, with SSO/SAML support and admin controls. Interactive mode: a brain REPL in the terminal with the same capabilities as Brain in ClickUp: skills (system and user-installed, so new skills show up automatically), memory, search across the workspace and connected apps, and write actions using the same confirmation rules. Headless mode: something like brain -p "..." --json for scripts and CI, with streaming output and structured results. Agent interoperability: expose Brain as an MCP server and/or agent-to-agent (A2A) endpoint, so Claude Code, Codex, Cursor and other harnesses can delegate work to Brain as a sub-agent. Today they can only call low-level ClickUp tools. Super Agents: invoke or chat with workspace Super Agents from the CLI. Local context bridge (opt-in): let Brain read files from the local working directory, so it can, for example, update a task with a diff summary or check a spec against the code. Governance: every CLI action shows up in the ClickUp audit log the same way UI actions do, permissions are identical to the web app, and admins can enable or disable the CLI at workspace level. Why it matters • Brain becomes the company's context layer for every agent, not just one more chat window. • Skills and memory built in ClickUp become reusable everywhere, which makes the Brain seat worth a lot more. • Without this, teams will keep piping ClickUp data into other models, and ClickUp turns into a database rather than the intelligence layer. Example workflows • In Claude Code: "ask Brain what the acceptance criteria are for this ticket and which compliance rules apply," then implement. • A CI step: brain -p "summarise this release and post it to the #releases channel" • From a terminal: brain "what's blocking the DK launch?", answered with full workspace and connected-app context.