When I start ClickUp, the first view is a random list which I don't often use. I would like to have the option to make "Home" my default view at startup. Many other users have expressed the same need (see : https://clickup.canny.io/feature-requests/p/set-default-location-when-opening-clickup-favorites-home-view )

Problem: Custom fields can become messy when you have different types of work (tasks) within the same lists. For example, having a bug, feature, and an epic task all in the same list would cause them all to have the same custom fields, even though I would want specific ones for each type. Other issues arise when fields that should only belong to the top-level task spread down to all its subtasks. Ask: Custom fields should have the option to be added to a custom task type itself. Whenever I create a new task of that type, it will come along with all its custom fields. Those fields will not spread to any task that is not of that type.

when we add a new task, if the task is already created before, a notification or an alert will let us know that this task is already created on the space level

It would be very convenient to have the ability to have subfolders. I use folders for classifying projects. For example, Projects would be a Folder name. 2019 Projects would be a Subfolder name.

Problem: Often within a single list, we have different types of tasks: some represent projects, designs, and smaller action items. Each one should go through their own set of statuses, but this is currently not possible. We are forced to either use dropdown custom fields as a workaround or create large status sets to try and encompass everything, leading to confusion among people. Ask: Give the ability for statuses to be set by type. This will allow each task type to have its own status workflow.

It seems that the opportunity to undo the previous action is only available briefly, while the "undo" pop-up is visible. It would be helpful to be able to undo previous actions using some on-screen button. Users may also be accustomed to using Ctrl + Z to undo previous actions.

Allow users to design a completely customized task view. The default task view "form" should be saved per task type and allow for overriding at the list level. Completely customizable - as an extreme example - a user should be able to set up a task view to only see a single checkbox custom field with no task name, no description, no other intrinsic or custom fields or relationships shown. The only feature of the task view form that should be required is a border with a close button. Stop assuming that the Status, Task Name, Description, Priority, or Due Date will even be present in the task view at all and let the user decide the grouping and sorting of all fields. Don't assume that because you have to do more processing to handle relationships the user expects them to be in a separate presentation from custom fields. The user should be able to pull in any property of the linked task as the value of the field, or a calculated or rollup value. The table of subtasks should be available as an option to insert at any point in the form. It should have customizable rollup columns. Or the user should be able to have a simple count of subtasks or calculated/rollup displayed if that's all they want for the use case.

We recently shipped Export to PDF. Spinning a separate thread for dashboard export to CSV and other formats

Examples: Be able to use Automations to change items such as Due Dates using relative dates, I.E. "Next Monday" "7 days before the start date..." "Each Monday..." When ANY date changes to ANY date Etc.