Feature Requests

It would be very convenient to have the ability to have subfolders. I use folders for classifying projects. For example, Projects would be a Folder name. 2019 Projects would be a Subfolder name.

It would be really helpful to be able to add a relationship between the task that triggered an automation, and the task that was created as a result of that automation. This would allow my team members to see the connection between our master tickets and the individual tasks that get created with automations as they move through our workflow without manually setting each relationship after the automation triggers.

It seems that the opportunity to undo the previous action is only available briefly, while the "undo" pop-up is visible. It would be helpful to be able to undo previous actions using some on-screen button. Users may also be accustomed to using Ctrl + Z to undo previous actions.

I've added this a couple of times, but as the team continues to use Clickup, there is a lot of items missing in tracking and forecasting. I've tried all the widgets but ideally this is what I need: for any given month (and possibly other time frames): a list of projects containing how much time was logged on that project by assignee or resource a list of resources containing how much time they logged on each project they worked on

Users want the ability to preview a template before applying it. Users want to be able to see what's included in a template at a glance. Comment below what information about the template is critical for you to see.

Assign a due date based on a number of business days ie be able to click Skip Weekends when automating a due date

From Josef: Remapping subtasks from parent task due date is great. But we also need it the othe way: whenever a subtask is delayed and rescheduled then the parent task due date should be updated according to new due dates for subtasks. Ideally the parent task due date could be auto-updated to max(due date for all subtasks) or due date for the last subtask in a chain of dependencies.

Allow team members to set leave or vacation dates, and prevent others to assign tasks on those dates? (Submitted via Intercom)

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.