Layouts by task type
future
Ivan Villa
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.
Log In
Ivan Villa
Hey there! 👋
Task types were just the start to help get different types of work organized in ClickUp. The team is working on various follow-up projects that will help make ClickUp tasks better fit the different types of work we manage.
I wanted to get this form out for those who want to be a bit more involved as we build out the next version. Whether you want to participate in betas or just want to be kept in the loop with designs, please fill out the form below.
P.S: Thanks for everyone's thoughts on the last post, a lot of great examples of things we want to help solve for folks here. 🙏
Caroline Ginty
Merged in a post:
Dynamic Customization and Fields by Task Type
M
Mike Smith
This request is two-fold. I would like to see more dynamic customization of the task view UI so that fields can be rearranged somewhat like the Boards View. I would like be able to change the task UI based on the task type--this is a big one because until we can customize fields based on the task type, task type might as well just be a tag of sorts.
M
Mike Smith
Further explanation for Dynamic Customization of Task View in general: I want to be able to move fields around, add tabs, have certain custom fields under each tab, rearrange the native fields, etc. This would give us more customization of the task view UI. By extension, these UI could be customized so that different task types have different UIs.
M
Mike Smith
Further explanation for Fields by Task Type: For instance, if my task type is a Contact, only fields that are relevant to a contact card (such as First and Last Name, Phone #, Address, etc.) should be visible. If the task type is instead an Invoice, we should be able to create fields such as "Add Expense" or "Add Fee" so that all of the other irrelevant fields are not visible.
Sebastian Oschatz
actually this gives a bold user story:
AS A customer I WANT TO move my customfields where i need them TO do my work.
Sebastian Oschatz
i understand that the 4.02 update now finally allows task types to be used as enumerated customfields with emojis.
as its a good practice reach feature parity before jumping into new unique new features -
any news on this topic?
Luci N.
marked this post as
future
Raina Ahuja
Merged in a post:
Custom fields display position
D
Devon Clark
Custom Fields are helpful. However, they're "second class" fields. They are displayed in the Details section - which requires scrolling down to view them.
It would be helpful if Custom Fields had a "Display with main header properties" property.
r
ronaldeager
Having Custom Fields show alongside the main header properties would make them feel less like secondary data, much like how the Pearl Lemon Scholarship Program emphasizes giving equal visibility to important details. Adding that option could streamline workflows without extra scrolling.
Emily Anthony
This would be amazing. Please make this happen, ClickUp!!
E
Erra Faye Zabat
marked this post as
considering
Hey, everyone! We’re excited to share that we’ve created new statuses in Canny to provide more transparency and clarity around the progress of feature requests. We've updated the status of this request to reflect the updated status. The Product Manager will provide updates on this post when they have new details to share!
Devin Shea
Erra Faye Zabat definitely appreciate the long overdo canny clean up. this one in particular not being marked as "future" is pretty disappointing, as this feels integral to the promised vision of CU. 😔
Natalie Williams
Devin Shea agreed. There are several existing features that need refinement to work optimally. It would be great if the CU team would prioritize resolving those ongoing (many times for years) community requests over adding more features. At this point, there should never be an issue with things like remapping subtasks not prompting, yet my team ran into that more than a dozen times this week alone.
Fix the bugs.
Refine & optimize existing features.
THEN add more features.
Load More
→