Feature Requests

Main task progress should be cumulative total of subtask rollup (similar to time rollup)

From support ticket: Would like to have all number custom fields rollup within subtasks to the parent task

Companies evolve over time, and so do workspaces. This means that custom fields can become less or more relevant over time. Similar to how we can archive tasks, I'd love to see the option to archive (but not delete!) a custom field. This would benefit companies with: * A lot of historical information. Who wants to store their information in one place (but not delete!) * A lot of experiments and want to store the results but avoid cluttering their fields simultaneously. * A fast-moving nature that evolves over time, and as a result, would like to archive a custom fields to keep things neat and tight.

Currently, ClickUp tracks how long a task spends in each status through the Total Time in Status feature, but this data cannot be directly referenced in Custom Fields or Formula Fields. It would be extremely helpful to make the time spent in each individual status available as a dynamic field. For example: Time in "Blocker/Stopper": 3 days This field should update automatically using the task’s existing Time in Status data, including the accumulated time if the task enters the same status multiple times. Ideally, users should be able to: Select a specific status. Choose between the current or most recent time in that status and the total accumulated time. Display the result in minutes, hours, or days. Use the result as a numeric value in formulas, filters, sorting, dashboards, and automations. The same data should also be available as a variable in Formula Fields and automation conditions. For example: IF Time in "Awaiting Customer Response" is greater than 48 hours, THEN change the task status to "Blocker/Stopper" Other use cases could include: Flagging tasks that remain in a specific status beyond an SLA. Sending a notification or assigning an escalation owner when an SLA is exceeded. Calculating the percentage of a task’s lifecycle spent blocked. Creating Formula Fields based on time spent in specific statuses. Filtering and sorting tasks by time spent in a selected status. Performing Dashboard calculations using specific Time in Status values. Creating more detailed workflow performance reports. This feature would significantly improve SLA monitoring, bottleneck detection, workflow automation, and deeper process analysis without requiring API integrations, external tools, or manual exports.

exp: I want custom statuses for tasks and, at the same time, simple statuses for subtasks

It would be so nice if we can apply formula on Row by selecting fields on which we can select against for formula?

Currently, updating custom fields on an existing task requires one PUT request per field (PUT /task/{task_id}/field/{field_id}). For tasks with 10-15 custom fields, that's 10-15 sequential API calls to update a single task. The gap: Creating a task already supports a custom_fields array in one POST. Updating should work the same way. Every comparable platform (Notion, Airtable, Monday, Jira) handles multi-field updates in a single request. There is no workaround. Automations are rigid, the bulk bar only handles one field type at a time, and middleware (Latenode, Make, Zapier) still has to fire N individual calls to ClickUp's API under the hood. Impact: -Integrations and automations are slower and more fragile than they need to be -Partial failures leave tasks in inconsistent states (5 of 12 fields updated, then a timeout) -Rate limits hit faster when every field is a separate call -AI agents (Brain, Super Agents) burn context window and response time making sequential calls that should be atomic Requested behavior: A single endpoint like PUT /task/{task_id}/fields (or extend the existing task update endpoint) that accepts an array of { field_id, value } objects and applies them atomically. Precedent: -ClickUp's own task creation endpoint already supports this pattern -Notion: single PATCH to page properties -Airtable: single PATCH with all fields -Monday: one GraphQL mutation, multiple columns -Jira: single PUT to /issue/{id}

Ability to set estimates in days, and how many hours per day, not just the total days/hours

It would be extremely helpful to have the option for subtasks to inherit a field's value from its parent, whether within the specific field's settings or via automation within a location.