1.6k
Custom Item Types (instead of only Tasks)
in progress
Y
Yuri
This is the next step in Clickups intended evolution from task list towards a flexible productivity platform. Item types allows to create names for items types and to create or select custom fields that are used by default for each item type.
In another feature request already the naming of 'item' has been proposed instead of 'task' but the current request is about the ability to create item 'types' that are available on the space level and down, which can hold their own set of custom fields.
This concept is the main principle in CMS such as Drupal which uses the term 'entity' and 'entity type' for its content, and since Clickup is a hybrid this would be a great improvement.
Log In
Michael
I'd encourage everyone to vote for https://feedback.clickup.com/feature-requests/p/start-date-notifications which will be superhelpful for Meeting "Items/Tasks"!
Andrew Watson
The ability to sort the created task types into either alphabetical or custom order is one improvement to consider for future releases :)
Roland Taracks
Ivan Villa Will task type be coming as a column? Main use would be table view where task type is currently not visible.
Ivan Villa
Roland Taracks: it is planned and should be a good solve for the table view gap we have now. Working to see where we can slot it in.
Spyder O'Neil
The different icons for each task type is nice! However, the update isn't useful in its current state. A custom field is more useful than this.
- As others have mentioned, no automations related to task type makes managing them a very manual and cumbersome process.
- It needs a better visual indicator than just the icon for easier/quicker identification. Since the icons for tasks change colors based on Status colors, they do not stand out in a list of other task types. It would be better if the entire line item/card could be outlined in a different color based on the task type...or keep the icon colors static based off the color you choose rather than their status.
- Set default task type for folders & lists.
Again, without the above, the task type update is far less useful than doing a custom field for task types (which is what I have been doing for the last year) since custom fields provide different colors and full automations.
Ben Porter
Spyder O'Neil: Default task type exists already for lists, but is still needed for Folders (and Spaces).
I think the inheritance from higher locations would work exactly like Statuses.
Spyder O'Neil
Ben Porter: Ah yes, folders and Spaces. Lists is solved, you're correct there!!
The other issues still remain and are bigger issues IMO. One could set default types to folders and spaces with an automation work around. It's what we've been doing with the custom field.
Manuel Montiel
So far I love the addition, however, the new "names" are still not carrying over to different views, such as the "Table" view.
Ben Porter
Manuel Montiel: Also not showing at the top of lists or for sub-items.
Also not showing in the task modal
M
Marza
Thank you for this one, this is great! I feel that it would be much easier to manage task types if we could group the tasks by task type. I know we can filter them, but it requires us to create multiple views so we can save this setting.
I
Igor Rusu
It would be awesome if custom task types have their own statues
Ivan Villa
Igor Rusu: Would you mind sharing your ideal setup? What types would you have along with what statuses for them?
Ben Porter
Ivan Villa:
There are some others that we might use in our workspace, but these would combine to create a Project. Each project would have one or more Quotes issued, with Invoices as subtasks. A Contact card would be added to show the customer for the project, and then of course you would have a series of Tasks to perform the work.
Much of this can be done with Tasks in Multiple Lists right now, but specifically the invoices as subitems of quotes is difficult if not impossible.
Task
* Not started
* In Progress
* Done
* Closed
Contact (Combined with a label of customer, vendor, etc)
* New
* Qualified
* Current
* Previous
* Disqualified
* Closed
Quote
* Draft
* Revising
* Sent
* Accepted
* Rejected
* Project Closed
Invoice
* Draft
* Revising
* Sent
* Partially Paid
* Paid In Full
pixojoy
Ben Porter: Woah, I like this. Statuses not being restricted to just Lists or Spaces could be very helpful.
Sascha Kirchdörfer
Ben Porter: Yepp, how do you know my setup?😉
Michael
Ben Porter: would you be willing to share your template at some point when this all comes together?!
Ben Porter
Michael: might be doable :)
Ben Porter
Ivan Villa: As I'm creating Task Types for our workspace, I'm realizing that sometimes you will want the Status determined by the Type, other times by the Location.
Most cases I can think of, it would be fine to configure this when you create the Task Type; either you select Statuses for your Type, or you leave it at "use Location Statuses". But there are situations where you'd want it both ways.
A decent example is a Content task type. I would create a status set to be used for these:
* Production
* Editing
* QC
* Published
* Retired
But I may want to make a list for Podcasts that need an additional status "Scheduled with Guest" or something, so I would want the Content items to get their statuses from the List if they were in that List.
Ivan Villa
Merged in a post:
Refined Task Types with names, specific colors and/or custom icons
Zachary Martin
I would like a way to easily distinguish one type of task from another. Maybe I want a certain type of task to be a journal entry and another type to be a regular to do, or another type to be an agile user story or another type to be meeting minutes or customer request or one just for those items that my boss asked me to do, or a general research note. So, I want to subclass the task object into different types, that are readily visible. So of course it would make sense for each list, to only allow one task type. It would provide a separate visible delineation apart from status and would further differentiate you all from the field. In fact, I don't know of anyone else that has this in the same space that you occupy. Azure DevOps has this but that is limited only to developers. I want a platform like yours for record/journal keeping as well as product planning and task tracking. (Submitted via Support ticket)
Rafael Healy Chacón
When setting a default custom type diferente than "task" for a list, Forms submissions from mobile (Android and iOS) can't be saved. Error (CUSTOM_ITEM_018)
Ivan Villa
Rafael Healy Chacón: Thanks for brining this up, we are working on getting a fix out 🔧
k
kerin barrett
Ivan Villa: I'm having the same problem. I also noticed when setting a default task type to something other than "Task" on the list, it's impacting an automation that I have which creates a subtask when task is created.
Michael
kerin barrett: Yeah I've been locked out of tasks until I change the name or something. Still some bugs to zap.
A
Aditya Harikrishnan
Ideally custom field should be set at a workspace level and should have customisable statuses, per item type.
Load More
→