I’d like to propose an option, that Asana could allow the project owner, to be able to completely turn off Asana notification for everyone, who gets involved in a project.
Here’s my scenario to show why it’s important
I duplicated one working project to test some ideas. I was the only member of the duplicated project.
I created a dozen new tasks and assigned someone to those tasks.
That someone was then overwhelmed with hundreds of emails.
Nobody wants their email to be flushed by Asana without a solution. It’s a pure disaster user experience.
From what I’ve learned after some searching, as a project owner, you can turn off notifications for project members only, not task assignees. Therefore, I’d like to propose, that Asana could at least add an option, for the project owner to be able to shut the Asana notification down completely, for anyone, via any channel.
And of course, I’ve got to mention it so that it’s clear for the product team, that the project owner can also turn that notification back on, at any time he or she sees fit (My experience in how Asana plays with the community is, sadly but truthfully, not quite pleasing).
Thanks for your reply. Unfortunately this is not applicable for my case.
Asana inbox thing requires additional action for the someone to operate, which is not part of their responsibility.
However, making sure that Asana send out just one notification only after the project page is up and running, is my responsibility.
I believe that this would be a general scenario where a project owner would hope to build the project in Asana, “quietly”. And notify everyone only once, after the project page is done.
Asana seems to have got the point by offering the option to turn off notifications for the project members. However, the notification to the assignee of a task still gets fired out, which, is out of control.
That’s why I’d propose to add another option, to turn off notification for everyone, be it project member, task assignee, etc.
And to turn it back on later, when a notification does need to be sent out.
This helps whoever working on building up the Asana page more in control of what he’s been doing.
To be honest that seems like really complex/hard to understand for a regular user, and would not count on Asana ever doing such a thing. But your post is in Product Feedback, that’s the right category.
A workaround for me now is not to use the “Assignee” at all.
I’d send a separate email to give the team a go, after I’ve finished building and testing the Asana project page.
This is actually more practical as some of the team members have filters in their mailbox to auto-archive all Asana emails, making them sometimes miss the system-generated notification.