Slack: Configuration: condensed attachments for subscriptions

Created on 4 Dec 2017  路  14Comments  路  Source: integrations/slack

Some feedback from an early user:

Not a huge fan of this integration
Way more info that I want
Really big on my screen
I just really like the concision of {old thing}

This was in response to a Pull Request opened notification, which included 4 failing statuses, and one summary status (3/7 successful checks).

No matter how much we optimize notifications, some users just aren't going to want all of the information to show up in chat. I think we should consider adding an option to subscriptions to only show condensed attachments.

I have not clue how it would work, but here's a suggestion to seed the conversation:

/github subscribe owner/repo format=condensed

subscription feature

Most helpful comment

Just chiming in to say our team also suffers from huge slack messages from the integration. We are very thorough in our PR descriptions with images, links and a ton of text explaining in detail what's been done. The problem is 1.5 messages take up all of our screens.

I saw this PR already addresses this issue: https://github.com/integrations/slack/pull/1046 and I was wondering if it's being merged anytime soon. We're at a point where we're going to remove the integration and fallback to copying and pasting the PR link because it's making us lose track of PRs.

Thanks!

All 14 comments

Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.

Yes, we just migrated from the legacy integration and this one displays much more information in our channel, which is distracting to our team. Also it includes the username of the user who opened the PR, which results in unnecessary notifications to that user.

Please provide an option to bring back the condensed-style notifications (2 lines if memory serves) used by the legacy integration.

My team wants condensed notifications also! We post screenshots and links in our pull requests, and the resulting Slack messages dominate our channel.

My team would greatly appreciate this as well for the reasons stated above as well as we use issue templates to try to get as much useful information as we can. These templates are formatted with a bunch of vertical whitespace to make them readable. This means that every issue fills up a huge amount of vertical space in the channel when they're posted.

@bkeepers I'm interested in diving into this when I have some bandwidth in the coming weeks, but I wanted to clarify one thing that's unclear:

I think we should consider adding an option to subscriptions to only show condensed attachments.

Is the concept of "condensed attachments" already a thing, or does the scope of this task require reviewing and potentially updating attachments across the entire codebase to support being rendered in a "condensed" mode?

Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.

Yes, we'd still love to see this feature back. For now we've turned off the integration in most of our channels because the notifications are too big/distracting.

My team also requested a way to limit notifications to just some types messages and those limited to one line, maybe two at best.

Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.

We still consider this relevant. We've disabled GitHub -> Slack integrations due to this regression.

Agreed, still relevant. We've had to disable this integration in many channels due to volume of text.

Super relevant for our team as well. This has basically turned one of our primary dev-centric channels into a PR notification channel

So tired of massive unfurls wrecking the chat.

Just chiming in to say our team also suffers from huge slack messages from the integration. We are very thorough in our PR descriptions with images, links and a ton of text explaining in detail what's been done. The problem is 1.5 messages take up all of our screens.

I saw this PR already addresses this issue: https://github.com/integrations/slack/pull/1046 and I was wondering if it's being merged anytime soon. We're at a point where we're going to remove the integration and fallback to copying and pasting the PR link because it's making us lose track of PRs.

Thanks!

Was this page helpful?
0 / 5 - 0 ratings