I have a couple of setups with a chain of dependent tasks. For example, when someone is creating an email, I have a set of tasks where once they complete the draft, it goes to other people for review, and those tasks are set up with dependencies.
Because of the volume of notifications that Asana generates, I usually filter it to show @mentions, and have advised the rest of my team of this as a way to reduce clutter & inbox overwhelm.
However, the current notification that a blocked task is no longer blocked does not include a tag for the assignee of the task.
It would be helpful if this particular notification type included an @mention with the task assignee’s name so that those notifications make it through the filter.
Furthermore I’d advise to see if you can eliminate the needless notifications at the source rather than filtering them for risk of missing updates that are important (like the one you mentioned). You can manage the default settings for new projects under Profile picture > Settings > Notifications > Project notifications where I’d advise to turn off the tasks added, and wal through the individual projects.
PS: As this is currently possible I’ve moved your topic to tips & tricks and marked it as solved. But be sure to let me know if this doesn’t work for you.
⚠️ Before you look at my answer to this I urge you to reconsider your plan. What is your real problem? Is it that you can't filter by looking for at-mentions, or the fact that you have so many notifications that you need to? Can you target the source of these notifications? Adding this rule everywhere will introduce more notifications and might lock you in to the problem. Also, it might make your way of working harder to change and improve. If you're still intent using this solution click the little triangle to expand this section.
How you can go about it would depend on your subscription tier.
At Enterprise(+) you could add the rule to a bundle, and add that bundle to all projects and project templates. You could also add the bundle to all projects in a portfolio at once. More about bundles here: Streamline work using Bundles
If not you could add the rule to all projects and templates, but I’d advise against it, as that is a lot of work, and would build a lot of resistance to change.
Agree, I’m not committed to it—I know it does add another notification, since the regular “this task is no longer blocked” notification would still go out, & it might create more problems than it solves.
I’ll see what makes sense & see if we can just handle this with better training & human processes.
And you have the right plan for it (Enterpise[+]), it might be worth including tasks to go through notification settings in a welcome project through custom onboarding
It hasn’t been mentioned yet, but you could have users who want this behavior to one-time-only add the unblocking rule to their My Tasks instead of worrying about applying it to all projects.
Thanks @lpb! I walk folks through setting up rules to move tasks into sections based on due date, but I appreciate the refinements you have here—especially adding a rule for tasks to move to New when they are unblocked, so that they are more readily visible! This is a great option for this issue that was raised. I’m going to share this article with my team.
