Feature Requests

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 a Task is linked, or a Custom Relationship is added, the Task name should be visible.

It would be great if in the Task View we could have the ability to customize (globally) the columns that we see next to each task. By default it is Assignees, Priority, and Due Date, with an option to manually add in columns, but that doesn't translate globally. I think a separate global setting for this would be a great addition as a lot of us are looking at start date and due date, not just due date.

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.

I'd love to see a task sidebar view that is fixed, rather than floating off to the right. Even on my laptop screen, there'd be enough screen real-estate to scrunch the main ClickUp view into a central column, and have a fixed/pinned task sidebar view on the right. I don't like how this sidebar view covers up the whole right side of the main ClickUp area. What if the information I'm trying to reference by using the Task-Sidebar view is only visible on the right side of ClickUp's main view? 😂 All in all, though, it's a great start, and it's very helper in many other use cases.

At the moment, task types are Workspace-wide. However, different teams have different needs as far as task types, which is why Space-level or private options would be optimal. For example, an HR team wouldn't rely on the same task types as an IT team. Each department may have sensitive information in their workflows (represented by a task type) that they don't want other teams to have visibility on.

Problem: We manage different types of work within ClickUp, and how sections are organized in ClickUp Tasks do not always work across each type. In some tasks, for example I want subtasks and fields front and center, while in others, I need to bring relationships front and center. Ask: Give the ability to have a different task layout for each task type. This would allow each type to have a layout that is better organized for that type of work.

I’d like to request a feature that allows the ClickUp AI Notetaker to recognize certain tasks with both start and end times as meetings. Not all tasks should be treated this way—only those specifically intended to represent meetings. For these selected tasks, it would be helpful to have full meeting-related functionality, such as automatic note-taking, transcripts, and summaries, similar to what’s available for calendar-based meetings. Additionally, this would require some UI tweaks to support full meeting functionality within tasks, making it easy to identify, manage, and interact with these meeting items. This would help teams who use tasks to schedule meetings directly in ClickUp, making the Notetaker more flexible and useful.

In Clickup 3.0 we can set "Default Task Type" in a list (Which is awesome). But it doesn't let you set default "subtask" types. e.g. - I want to make a "Person" task type for the default in my List, but I want each Sub-Task of those "People" to be an actual regular Task. (This will help me utilize CRM style functions, while letting those subtasks show up in my everything view as actionable tasks, without showing the CRM lead name, since those aren't actionable tasks...)