Awesome! I’ve updated my formula and think it’ll work that way. Thank you all so much for your help!!
2 Likes
Just moved over to Asana from Monday.com and I’ve read through this topic.. Just wondering if I might have to move back to Monday if Asana can’t do the below:
Trying to add custom date fields and set up rules to automate things when that date is x days away. For example, email me when manufacture date is 14 days away. Change priority when install date is x days away and more along those lines.
At the minute all I can see is that I can do this with Due Date (when approaching) or Start Date, but not with custom dates?
This topic has been here for 3 years so hoping this is implemented by now
1 Like
Hi, @Mark_McCormack .
I have never used Monday, so please explain.
Are you requesting the following?
- Why do you care about custom fields?
- What kind of problems are there with due dates?
- Why is it necessary to set a specific date other than the due date, and then execute a different action when it is X number of days before that date?
It’s necessary for me because we have several important date points on a project timeline, not just a start and end date. I use automation in Monday to notify me when it’s 4 weeks from installation date to carry out quality control checks and make sure all components are ordered/in stock etc..
Basically we use 3 important dates that, at the minute, I can automate notifications/emails to be sent x days before those dates. I can’t do this in Asana it seems, only with Due Date or Start Date. It’s just extra flexibility that seems like it would be useful in general and is available in other software like this.
1 Like
As I understand it, the task (event) has a due date, and a sub-deadline is required 10 days before the due date. Is that correct?
Is the following correct as an example of how it works?
- Event task: Due date = August 14th, Alert days = 10 days
- Notify the person in charge on August 4th, 10 days before August 14th
To get straight to the conclusion, it was possible to achieve this using rules.
I will add more details later.
In that case, an alternative solution would be to create a follow-up task for the event task and set the due date of the follow-up task ten days before the original task.
It might be better to set a dependency between this event task and a follow-up task.
The “Asana way of doing things” really focuses on a task’s due date in these cases, so as @Ka_Nishiyama mentioned above, the general solution in Asana would be to create multiple tasks - and quite possibly make those subtasks - to track the other related dates.
Having said that, it is possible to do what you’re wanting in the rules of our Flowsana integration, for example:
1 Like