Task-specific rule functionality seems like a pretty obvious and necessary feature. Especially, without a rule that can tie custom fields to specified sections. The rules are too global to effectively automate recurring tasks across multiple cycles and departments when categorizing sections temporally.
1 Like
An interim solution is to add an additional task field - Single Select, and set multiple options within it. Then, in your Use Case Three, simply add an additional trigger, task field=needed specification.
Example:
Triggers: Task unblocked and Project Section = SVI
Action: Set due date to ___ days from now
Specific rules would reference different âProject Sectionâ stages, (SVI, Adequacy, etc) and different due dates would be specified in the action accordingly.
Any update on the task-level rule functionality? Itâs been over two years since the issue was first raised in this thread. Thanks.
2 Likes
seriously its ridiculous! But theyâve changed fonts and colors 24850808 times in two years 
This is a bit ridiculous to have open for this long⊠When you donât have basic filtering functions for triggers (ie. only run if task has xxxx in name, or if task has priority of y), the rules are essentially useless.
A post was split to a new topic: Rule trigger for subtasks complete with task in a section
+1 rules without filters are pretty useless.
This is a super basic function that makes me wonder why weâre paying for a Business account. We shouldnât have to involve a third-party app (hurtling another paywall) for something as simple as âwhen THIS TASK has THIS THING changed/added/removed, do THIS.â
I donât have a single use case to support rules affecting every task that touches a project, and it sounds like most other users who have commented feel the same.
7 Likes
In order to automate process flow between different assignees, it would be great if we could set up a rule for specific tasks - ex. when specific task 1 is complete, variable or specific person is notified.
2 Likes
I spent so much time looking for this feature b/c it seemed so obvious it should exist, and I thought I was just missing it. The concept is brilliantâŠbut only on a task level. Task specific rules would make my project template 1000 times better and save me so much time!
PLEASE, is there an update on this? Is there movement? Is there a projected time of when this will be available?
7 Likes
It would be great if we could create rules based on individual tasks or subtasks.
For example:
Set due date on subtask 2 when subtask 1 is marked complete
2 Likes
Welcome, @Carl_Littrell,
Iâve merged your post into an existing thread where you can click the title to scroll to the top and vote by clicking the purple Vote button.
Thanks,
Larry
1 Like
We would use this feature all the time to send slack messages to channels only when a specific task or subtask is completed, and not everything within a projectâŠ
2 Likes
Any movement on this yet? Iâve been eagerly awaiting this feature for a long time now.
2 Likes
Agreed that this feature is critical for being able to send Slack messages about SPECIFIC tasks without having to involve expensive AI to do this. A simple task text âcontainsâ rule would be enough and should be simple to build.
1 Like
Any news on this?
I need a specific task completion to trigger another task creationâŠ
1 Like
@InĂȘs_Guedes_Marques - I just use a single/multi-select field (with either a single checkbox or option for each rule I want to run on the task) and use it as a condition in the rule
1 Like
is there still no update on this feature?
It would be very useful to create automation rules at the task level, not just project or portfolio level. For example:
- When Task ABC is completed, automatically set Task XYZâs due date to 7 days later.
Currently, this requires awkward workarounds with dependencies or preset template due dates that are trying to predict the future, which donât reflect real timelines. Task-based rules would make workflows far more accurate and efficient.
Iâm assuming you mean for in project templates, as otherwise it would only become more in-efficient.
A workaround suggestion:
- Mark the tasks you want automatically updated with a custom field value
- Block that task by the preceding work
- Create rule: When task is no longer blocked, check if task has the required field value, then set due date for trigger date +7 (or +5 if you use 5 day project work schedule)
Shifting using different timeline dependency settings might also work.