This is too broad. Channels can be used to logically segregate integrations for continuous monitoring/reporting, but within those channels there can be more granular options to mute *specific integrations.* That is the use case and how the story should read. "Mute individual users" is far too broad and suggests muting human users that can hinder the overall collaborative efforts of your team.
But this is an important feature. Without it, the running solution is to split channels in to more channels, and that can clutter your left pane with an arbitrary number of channels, whilst this feature would relegate alerts to one channel and selectively mute the alerts that are not relevant to you
Sean
This is too broad. Channels can be used to logically segregate integrations for continuous monitoring/reporting, but within those channels there can be more granular options to mute *specific integrations.* That is the use case and how the story should read. "Mute individual users" is far too broad and suggests muting human users that can hinder the overall collaborative efforts of your team.
But this is an important feature. Without it, the running solution is to split channels in to more channels, and that can clutter your left pane with an arbitrary number of channels, whilst this feature would relegate alerts to one channel and selectively mute the alerts that are not relevant to you