Hey there, just checking in if we do have an update regarding enabling scheduled/delayed comments feature in ASANA?
1 Like
You really need to consider implementing a schedule send in Asana, specifically in the task comments.
If I can’t sleep so I log on and complete a task at 2am, I don’t want anyone getting alerts at that time or seeing that I was up at that time. So what I have to do now write the comment in advance but wait and hope to remember in the morning that I need to send it. However, everytime I tried to save my message for the morning, I forget to send it altogether.
Having a schedule send also helps us to send a message at the best time. If I send something close to lunch, it may get overlooked completely and by the time they’re back at their desks, my message is buried and dead. Same thing for any message I send after 5 or 6pm.
And if there’s a specific reason you don’t want a schedule send button. Then instead of a schedule send, you can set a temporary delay. Set up some checkpoints where a message can only be scheduled to send at, like 9am, 1pm, & 5pm. So instead of scheduling to send at any time, you’re simply delaying it until the next checkpoint. The point is we need you to be implementing something… or anything along the lines of a delay or schedule send. Thank you.
2 Likes
I am voting for this “Schedule” feature because many times I have to do my work after office hours and wanted to update my tasks with comments on next morning but I can’t schedule. I schedule things in slack, but am unable to schedule in asana which I find weird!
Please introduce this feature!
Hello. Is this something that’s in the works? Multiple users have been requesting this feature for years now. Any updates?
1 Like
Welcome to the Asana Community Forum @Evlyn_Littlejohn 
I recommend leaving your vote by clicking the purple “vote” button at the top of this thread. And here is some info on how Asana is listening to product feedback.
Voted! This is so important for all the reasons noted above. Scheduled comments is fundamentally different from notifications.
One workaround I’m doing now is just creating my comments in different asana windows and not sending them. Then making sure I have one “Home” window open on my main monitor, that has the widget for reminding me about draft comments I haven’t sent. At the beginning of my next work day, it reminds me to go through all those windows, send the comment, and close them.
So we know Asana knows that we have draft comments and keeping them in a buffer somewhere. Please add the function to send them later so I don’t have to have all these darn windows open.
2 Likes
I can see how adding this feature might complicate the workflow when tasks are “completed” but delayed in sending or when new tasks are “added” but delayed. I could see unintentionally creating duplicates or it getting confusing if someone “completes” in the meantime while another action is delayed.
For comments though, this seems feasible and is a good way to keep the work going on off hours but providing quick updates or check ins. Please ADD!
1 Like
This ^
It must be worth it for the other major platforms who choose to provide this feature.
Definitely, in my opinion this feature promotes toxic behaviour and I understand some platforms might decide not to release it.
You can do that when you’re commenting to a thread via email, for sure, and I do. That is another great byproduct of “reply by email” on Asana. But I use and communicate more on Asana via a browser or the app on my phone, at which point I lose this simple and powerful feature.
So you think this feature is a bad business/product decision and you think it promotes toxic behavior from users. How does it promote toxic behavior?
Glad you asked, I know this feels counter intuitive.
Delaying a comment seems like a good idea: you work late, you don’t want to notify your colleague.
But, bear with me. Let’s look at 2 examples:
- me working with my colleague @Julien_RENAUD on the same timezone
- me working with my colleague @Kelsea_Lopez in the US, on different timezones (I am in France)
My belief is that:
- Julien works at 10pm and delays his comment so I receive it the next day: it puts the burden on him to do the work by using the feature, if I am also working at that time I don’t get to collaborate right away, it doesn’t show that he worked late so I can’t detect he is doing after-hour work and potentially have a discussion with him, and it also doesn’t force me to have a healthy notification setting
- Kelsea works at 4pm on a task in Asana, is she supposed to delay any comment on a task where I am a collaborator because I am asleep? of course not, do you imagine the burden? and when I work the next day at 9am, should I delay my comments if she is on the task?
I believe this feature promotes toxic behaviour because it will allow people to work after hour without showing it. As a manager, if my team works at 10pm, that’s a red flag. It can happen once or twice, but this isn’t healthy and I want to be aware of it to have a discussion with them. Why did they feel the need to work this late? What can we do to make it better?
And if that notification woke me up, that’s my problem, that means I have an unhealthy notification setting.
So this feature, instead of protecting employees receiving notifications, it allows people to hide unhealthy habits.
Finally, and this is very controversial and a personal opinion: I am the co-founder of the company so if I want to work during the week-end, that’s my choice. I am not an employee, I don’t have a contract, you don’t get to build a company by working 9 to 5, and I don’t want to delay all my messages. Who am I fooling when my team receives all my emails at 9am Monday morning? Everybody knows I scheduled them during the week end 
But my team is protected by laws, they have a right to disconnect, and they should express that right by having the appropriate notification settings. I don’t expect them to read my emails during the week-end or open Asana.
2 Likes
Thank you for this. Understandably, it all focuses on notifications and time zones and what it means for how we work together. I would say that your 2 examples are good ones and point to the need for different teams to work out their own unique SOPs for time zones and work. They can choose to use (or not use) a schedule send feature and I would posit that this is very reason to have such an option.
But also important to note is that this is not the only use case for this feature. We use schedule send extensively on other platforms to sequence and pace our work around media production. In this case, it’s not about when our colleagues or partners are working, but when we want to communicate something and in what sequence.
You suggested that we create drafts and then go back at a later time and send them. This pretty much defeats the purpose of schedule send bc you would need to remember the timing for each draft. Another limitation to using drafts is that you can only do one draft on a thread at a time.
5 Likes
Adding my +1 here. I’m prepping for the week on a Sunday and would like to check in with collaborators first thing in the morning, but not pressure them to respond on a Sunday. Scheduling a comment would be so helpful to not perpetuate the expectation of “always on”.
2 Likes
Make this happen, Asana. It’s a feature many of us would like, and it’d differentiate you further from other work management systems.
1 Like
One of us starts work at 5AM, others start at 9AM, others finish at 5PM, and still others at 8PM.
Slack, Business CRM Email, and other project management tools understand it is important to be able to schedule replies for various reasons both functional and cultural, and have prioritized this feature. Again, mass adopted communications tools, have prioritized a schedule-send feature, this should be telling to Asana.
Not having this feature prohibits our best work being done, and results in user frustration at Asana as a tool when it so so commonplace elsewhere.
1 Like
It is funny that to me this is exactly the argument for not needing such a feature. We all have such different working hours, not even talking timezones, you really want to put the burden on the sender to remember when the other person is working? What about a task where you have several collaborators, do you account for all of them? I don’t want a world where all notifications come in at 10am at once because everybody’ understand it was the “best” time…
Just another request for an option to schedule comment send similar to Slack and many others - I wrote a comment after hours and literally had to leave the browser open for the weekend so I can go back and pick ‘comment’ on Monday. THEN I got an email asking if I forgot to finish my comment. Talk about tone deaf. Very frustrating, I would much rather have simply scheduled it to send at 8 AM on Monday.
2 Likes