Skip to Main Content
Status Likely to implement
Categories Slack
Created by Guest
Created on Jul 24, 2015

Improve Content of Slack Notifications

Currently Aha notifications in Slack are not very human readable.  For instance, when requirements are added the product, feature name and the description are not present.  It's impossible unless you're the author to know what the requirement relates to.  

Release time frame 3 months
  • Attach files
  • Emily Rittenhouse
    Reply
    |
    Apr 24, 2024

    It would be great to be able to add Feature Description to the Slack notifications. Right now, we alert the entire company when a feature changes statuses. We'd love to be able to attach the Feature Descriptions so employees can see the context at a glance.

  • Dave Tucker
    Reply
    |
    Sep 11, 2020

    I have a specific requirement to send the Idea Category field through to Slack. I’m told by Aha engineering that this is not available at present but it’s essential for my situation so we can easily assess who should respond to the idea without logging into Aha.

  • Jim McIntosh
    Reply
    |
    Feb 19, 2020

    I'd like to configure the fields that are returned in the slack message per event so that it's easier for people without access to the Aha issues to see the context of the change or request. For the initial request, I'd have the idea name, description, and the custom field for the user. For a vote, I'd select the idea name, custom field for the user, and the vote. For comment, I'd have the idea name, and comment, and user. 

  • Guest
    Reply
    |
    Dec 11, 2018

    The ability to choose what information is visible will greatly reduce noise and increase readability/usability of these Aha Channels in Slack. 

  • Steven Petryk
    Reply
    |
    Jun 29, 2017

    Relatedly, the Slack integration currently sends messages (sometimes) out of order, but also always sends multiple messages even when only one thing was created. A nice improvement might be to consolidate these into one message to reduce noise.

  • Guest
    Reply
    |
    Feb 10, 2017

    As a user of Slack, when Ideas and Features are added to my board (that I'm responsible for), I want a short, tight summary loaded into a slack channel. It's a big pain to have to sort through emails, plus slack is already channeled for this type of work. I get too many emails as it is, and I'm not in a position to change this in my company. 

    Allow me to control the way the AHA-->Slack message shows up in Slack. I'm a Product Owner, not an admin, so don't limit this to admin functions either, which will equally suck.

    PS. Trying out emotional user stories...I really mean the emotions, but not use to documenting them. 

  • Bryan Crist
    Reply
    |
    Feb 3, 2017

    Ideally, I could configure what data I want sent in my Slack notifications for an activity. For example, when I set up a notification based on idea name, it sends the name, workflow status, score, visibility, assigned user, and number of endorsements. I'd like to be able to set it to send the name and description. Or name, description, and status.

  • Jonathon Leeke
    Reply
    |
    Feb 18, 2016

    I'd like to be able to push out shipment notifications to Slack for releases with a list of features, similar to what watchers would get via email.

  • Pierre Sauvignon
    Reply
    |
    Feb 18, 2016

    I agree that some work is needed to make the Slack integration useful (and not harmful).

    Unfortunately at the moment the level of detail Aha! ends up pushing to Slack tends to quickly saturate the channel with pages of unnecessary data. That triggers a damaging user behaviour: User scrolls quickly through it and therefor misses out completely on the info.

    My approach is that a Notification is a brief bit of text, NOT a complete account of every single piece of available data. If a user wants the details they click on the link and find the details in Aha!.

    I understand that others might have different needs so as to what is the valuable piece of information. Hence the ideal solution is likely to be about allowing users to select what information is part of the notification.