đź”” More control over project notifications in Slack

Asana Community Product Announcements Product Updates
,
1

Hi Community,

Slack project notifications are officially out of their all-or-nothing era!

A lot of the feedback we’ve heard over time pointed to the same pain point: project notifications were too rigid. Some of you wanted to choose which updates showed up in channel notifications, some wanted status updates to land in Slack, and others wanted comments to come through too.

We’ve received many comments in threads like Limit Notifications in Slack when Project Linked and Reducing/Customise Asana Notifications in Slack, Status updates to Slack, all surfacing versions of that same ask.

Now, you can set up and manage project notifications directly in Asana and choose exactly what gets sent to Slack.

1055Ă—1156 56.9 KB

:sparkles: Here’s what’s new:

  • Set up project notifications from Project Settings in Asana instead of managing everything only from Slack or Teams
  • Connect a project to one or more Slack channels
  • Choose which notification types each connected channel receives, including:
    • comments
    • status updates
    • task additions
    • task completions
    • assignee changes
    • due date changes
    • field changes
  • Give stakeholders the updates they actually want, without flooding a channel with everything

A few helpful notes:

  • Project admins and editors can set up, edit, and remove these notifications in Asana
  • For private Slack channels, the Asana Slackbot needs to be added before the channel can be selected
  • This update is focused on Slack for now

:yellow_heart: Why this matters:

This makes it a lot easier to keep the right people informed in the tools they already use, whether that means sending new request notifications to an intake channel, posting project status updates to a stakeholder space, or celebrating completed work with the team in real time.

And it closes a long-running gap in the experience. Instead of choosing between too much noise or no visibility at all, teams now have a lot more control over how project updates show up in their communication channels.

Looking ahead, there’s still room to make this experience even easier to discover and manage, but this launch is a big step toward giving teams more control where they need it most.

If you were one of the people who weighed in on any of the feedback threads above, thank you. Your feedback helped shape this one.

Hope you enjoy it, and feel free to share your thoughts and questions in the comments.

6 Likes
Status updates to Slack
Limit Notifications in Slack when Project Linked
🎉 @mention Asana in Slack to create tasks and get answers
2

Great, more people can work from Slack and never set foot in Asana :sweat_smile: #troll

3 Likes
3

@Bastien_Siebman nah, it’s more like Asana following you all wherever you need us to go! :laughing:

Worst comes to worst, here is our message to everyone :smiling_face_with_three_hearts::

4

Wishful ask…are we able to setup these notifications and channels via the API or perhaps using the Asana AI? :smiley:

Otherwise, I’ll hope I’m allowed to crack a bevy while I manually configure our few hundred projects :clinking_beer_mugs:

6

I find the Project Update reposts feature barely usable. How can I best request improvements?

  1. The status update includes and duplicates so much metadata at the beginning that very little of the update actually makes the cut before Slack trims it with “Show more”. Can you make it so that my name (who posted the update) only shows once? So that there’s less space wasted by the obligatory Summary header?
  2. The repost fails to translate formatting from Asana to Slack. Instead, it dumps raw markdown or similar characters, and completely fails to represent nested bullets correctly. Can the posting process actually post formatted text?
  3. In a project that is not globally readable by the org, every link to a task within the project shows up in the Slack update as [Private Link], making the flow unreadable. Why doesn’t Asana trust that if I’m choosing a #channel to receive project updates, it should at least be able to see task titles?
7

Hi @Arthur_Prokosch , best to create a new thread for EACH of your points, in the English Forum > Product Feedback category.

Thanks!

8

I’ve recently set up this to work on a couple projects and noticed that for status updates, I need to configure that in two different places. First, in Project Settings > Notification settings I set it up to allow Slack to send status updates to a channel. Then when I tested updating a project status nothing happened in the channel. Only after I added the Slack channel to the “Connected Channel” field when making the status update did it push in to Slack. Is that duplicative configuration step expected functionality? If so, I’d love to request a feature improvement so that if the notification settings connect status updates to a specific channel, that “connected channel” is automatically populated when updating the status.