RELATED IDEAS
Allow custom due date options for to-do automation actions
Who would benefit? |
Users who are looking to automate the creation of to-dos, approvals or work requests |
What impact would it make? |
Allow more flexibility in to-do creation |
How should it work? |
Similar to how we can select the custom date option when creating recurring to-dos, we should be able to select custom due date values when setting up automation rules where the action is to create a to-do. Today the options are preset which can limit the ability to fully translate to-do creation into automation actions. |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
© 2025 Aha! Labs Inc.•All rights reserved
Similar to other comments, when creating to-dos via automation rules, we would like to be able to set the due date relative to the related record. For example: in an activity automation rule, set the to-do due date to the same day as the related activity's due date. It's not feasible, in our case, to use a fixed time frame from to-do creation, because the timeline for the to-do varies based on the scheduling of the activity itself.
We have static Start and Due dates to our PIs and were hoping to automate the date settings on Features using those dates based on the PI picklist value selected on Features. Unfortunately, this is not possible through automations which means the team members will need to manually set them. Please add.
This is SUCH an important need for creating truly flexible workflows. I have workflows that are approximately 8 weeks, so the automation falls apart after week 1 for all tasks past that point of kickoff.
The current options for to-do timing are very limiting, as they are all relative to the date that the trigger action occurs. We would like to be able to assign due dates relative to other fields (for example, when trigger <x> occurs, create a to-do with a due date 10 days before the Activity/Feature start date)