Feature Requests

Need ability to restrict who can and cannot see and who can and cannot change Automations. Automations should still be able to run when conditions are satisfied, but their existence should be made invisible to selected users or roles if/when necessary.

Problem Automations only ever act on the task that fired the trigger. When a subtask is created, there is no trigger that fires in the context of the parent, and no action scope that lets me modify the parent. Any parent-level state that depends on the existence of subtasks has to be maintained manually. Request New triggers, evaluated on the parent: Subtask created and Last subtask removed. New action scope: apply the action to the parent task — change task type, change status, add/remove assignee, set a custom field value, add a tag, post a comment. Use case In our workspace parent tasks are containers, not units of work: only subtasks are assigned and only subtasks are billable. As soon as someone breaks a task down into subtasks, the parent should automatically have its Task Type set to "Parent Task" and its assignee cleared. When the last subtask is removed, the parent goes back to being a regular assignable task. Today each PM has to remember these steps manually. A missed one corrupts workload reporting and billing exports, because an assigned parent gets counted alongside its own subtasks. Why the current options don't cover this Task created fires on the subtask itself, and every downstream action applies to that subtask only. A generic "subtask removed" event would not help either — the parent must only revert when no subtasks are left, which is why the second trigger is scoped to the last one. The only workaround today is an external service polling the API for parent/child changes, which is not viable as a workspace-wide convention. Impact Unlocks a class of parent/child governance rules that are currently impossible natively: ownership normalisation, task-type normalisation, roll-up field maintenance.

I have many automations with descriptions, and scrolling through them to find the one I need is a pain. It would be helpful to have a 'Search automations...' function, similar to the 'Search tasks...' feature in views.

From Support Ticket: I can't automate status change or anything based on email thread (eg WHEN New Email received THEN change status)

It will be nice to start timer from automation and stop timer from automation as well.

Add a trigger option for removal of tasks from a list. Use case: I want to change the task type back to a regular task when removing a task from the current list. This is not the same as deleting a task. The task still exists, it's just serving a different purpose now and being tracked in a different way/location. Therefore, I want to automate the task type switch to ensure that the fields align with the current function of the task without having to duplicate the task.

A growing project can become difficult to follow when information is scattered across too many places. Teams working on accounting firm seo services https://pearllemonseo.co.uk/industries/accountants/ often have several related tasks moving forward at the same time. The challenge is not always having more tools, but making the existing workflow easier to understand. A task should clearly show what needs to happen and why it matters. This becomes especially useful when work passes between different people before completion. Simple status options can provide a quick picture of what is currently in progress. Clear task descriptions can also prevent repeated questions and unnecessary back-and-forth. Another useful feature is the ability to connect related tasks without making the workspace complicated. Dependencies can show when one unfinished item is holding up another piece of work. Notifications should provide useful reminders without creating constant distractions. Good workspace organization also depends on being able to find older information quickly. Search tools can save considerable time when projects contain hundreds of tasks and discussions. Filters are equally helpful when someone needs to focus on a specific priority or deadline. Recurring work can benefit from consistent structures that do not require rebuilding tasks each time. At the same time, users should be able to adjust those structures when circumstances change. Flexibility becomes important when different teams approach similar projects in different ways. A useful workspace should make progress easier to recognize rather than adding another layer of administration. Small interface improvements can sometimes have a larger impact than major changes. Reducing unnecessary steps can help people spend more time completing work instead of organizing it. Feedback from everyday users can reveal these friction points more clearly than assumptions can. The most valuable improvements are often those that remove a repeated inconvenience from a normal workflow. Better visibility can also make collaboration easier when several projects are active simultaneously. When information stays connected, teams have fewer reasons to search through separate conversations or documents. That creates a workflow where organization supports the work instead of becoming the work itself. Continued attention to these practical details can make project management feel considerably more natural.

Currently I can stop or delete automation only from the list of automations, but if I am inside the settings of automation, I can only save the changes, but can not stop or delete it. I usualy find automation from action window within the task actions, so I want to pause the automation from this place.

Hello, there is an automation trigger when " A comment is added" as the top level of comments, but we cannot control the users who comment on our tasks and most probably they are used to commenting on a thread which results in automation not triggered!, so indeed we need to add the threaded comment inside the main feature as a checkbox so we can be able to enable or disable in each automation