*Note: this request concerns organizing custom fields into groups, not grouping views by custom fields.
Currently we have the ability to set custom fields at the Space > Folder > List levels, but it would make sense, and be immensely helpful, to extend that capability one level down to the task level as well. One idea – and perhaps the easiest to implement - would be to simply allow organizing of custom fields into groups with the ability to collapse groups (e.g., unused groups) at the task level.
Setting custom fields at the space level, with the ability to customize at the folder and list levels completely makes sense, but there are, in many cases, a variety of task types at the list level that don't need to share the same custom fields inherited from the list where they live.
To give an example, for my industry I track real estate transactions (purchases and sales) on a per client basis, with the client name at the folder level, plus specific real estate transactions at the task level, in addition to other types of information related to the client and their history as a current client.
After fairly extensive experimentation and trial and error, I have 4 types of tasks (indicated by status) that are tracked at the folder (client) level:
  • Client Data (for general client info prior to making a purchase or sale)
  • Transaction Data (for specific purchases and sales to track contract terms and deadlines)
  • Tour History (for logging a history of properties a client has toured)
  • Offer History (for logging offers to purchase, made or received by the client depending on if the client is buying or selling a home)
Because of the extensive data related to a real estate transaction that needs to be captured (to track contractual terms and deadlines, in addition to performance data for the team dashboard), the list of custom fields is pretty long. But we don't need to see that full list for the other three types of tasks that are being tracked at the folder level. It's not a deal breaker, as custom fields is largely what makes CU a viable alternative to other platforms like Airtable, but it does add a layer of clutter and perhaps complexity that just doesn't need to be there in many cases.
Here's a loom video showing how my list of custom fields displays on a task (the list is too long to take a screenshot):