yes please. some times my team needs a reminder days before the due date

1 - exact dates would be most helpful for selecting "if due date is "Saturday" or "Sunday" -> do XYZ. Our main team workflow is to import a task template, select a new parent due date then auto reschedule subtasks BUT this causes some subtask due dates to fall on the weekends. It would be ideal to have an automation that scans for subtask due date falling on a weekend, to reschedule the due date to the following monday & push all subsequent subtasks into the future as well.

2 - the scheduler tool/recurring date functionality would be helpful to check if subtasks or task have due dates that fall on the weekends. I could see us setting that up to trigger every Sunday, for example.

Recurring date is incredibly helpful. Please include this!

As for "exact date" - I still think this can be a very useful feature - so if it doesn't cause any negative effect to include then I would say just include it!

I 100% agree with other comments that dynamic due dates will be a pivotal piece to this feature.

Re: 1. "How critical is "exact date" as an option for a "The current date is..." trigger?" I don't see a need for this; seems to add too much complexity to this system... for the 1% of users who might want this, perhaps make an "advanced" features option to display this

Thank you for this exciting development! It looks like the new calendar/scheduler feature addresses the need for an "Exact Date" in automations, and we can now leverage "Due Date" instead. I don't see a particular need for "Exact Date" moving forward.

I’m curious about how the scheduler function works with tasks set to 'recur forever.' When the Due Date of such a task arrives, does the system automatically adjust it on the day after, or does it require marking the task as 'Completed' to trigger the next due date? I noticed there's an option to 'create new task'—which seems relevant to my question. What would be the advantage of using a 'recur forever' task versus the 'create new task' option? Looking forward to learning more about this functionality.

Additionally, I agree with Bryan Su's (scheduler) and Daniel Gonzalez's (parent task) suggestions for achieving optimal functionality. Volodymyr Kryzhanivskyi's insights on Monday's triggers also opened my eyes to expanding possibilities with automations. These all cover a wide range of workflow needs.

I would like to request that relative trigger dates for automations be available for any date custom field as well as start and due date fields. Thank you!

Looking at your video and considering the feedback already given, we believe that covers our requirements. For us an exact date would not be necessary for a trigger and a scheduler would be brilliant. Being able to select items say 7 days before the due date and then an action being taken would be great. In advance rather than an automation taking place once the due date has been reached. Hope this helps.

The recurring date is interesting. The exact date I don't see as useful

Hi! After reviewing the video, I feel that all the use cases you showcased are valuable and useful. However, I do think it'd be of great help if we can have dynamic dure dates relative to a Parent task. For instance, in software development, you might plan a release for, say, Sept 10th. But you need QA (a subtask) to be done 2 days before release, Development (another subtask) 5 days beofore release, Design 8 days before release, etc.

So, as you can see, all would depend on parent task's due date. Will this be implemented here? If not, is there a way to get Subtasks to inherit the parent task's due date? (That's a workaround so we make this automation less complicated).

Recurring tasks work just fine.

The other options that depend on a custom date field or due date are fine.

For me there is two type of scenario:

Automation for Recurring Tasks: The automation should allow tasks to be set on a recurring schedule, such as creating tasks at specific times each month. For example, if I need to send a report to client ABC on the 10th, 15th, and 20th of every month, I should be able to set this up once and have the system automatically create and assign the task to my engineer. This repetitive work can be automated, saving time and energy from having to remember and manually create the task each month. Currently, there's no way to do this with automation. With your method, I would have to create a list with tasks and their due dates, and let automation create tasks based on those dates. However, this isn’t a true recurrence, as I would still need to manually update the due dates each month.

Automation Alerts Before Due Dates: Automation should be able to trigger alerts a certain number of days before a due date. Triggering automation only on the due date is often too late. For example, if we manage 1,000 domain names with various renewal dates, we need to take action before the domains or SSL certificates expire. The list serves as a record of start and expiration dates, allowing engineers to act promptly before expiration. If automation could detect upcoming due dates and create tasks for the engineer X days in advance, it would be ideal. Currently, I have to assign an engineer to manually monitor these dates each month.