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.

With the new filter inside tasks it would be amazing to be able to set default options to only save specific filters while inside tasks. For instance default to only see comments or attachments.

Add the option to include custom fields in the top section of tasks alongside things like due date. We use custom fields for critical parts of our tasks so having this info visible at the top of the task would be very helpful.

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.

By default are comments sorted from oldest to newest. When long conversation is happening, you must scroll to the bottom to see latest comment. More logical is latest comment on the top. But as everyone need is different, it will be great if everyone can set default sorting of the comments as per his needs.

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.

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.

From support ticket: Import Nested Subtasks via CSV