action #178897
closed
Refined use of team-qa-tools Slack channel for automatic notifications size:S
Added by okurz 20 days ago.
Updated 1 day ago.
Description
Motivation¶
Based on retro item from 2025-03-14. We have multiple automations writing sometimes overly verbose or also duplicate information into our Slack channel "team-qa-tools". Some examples:
- Too verbose: progress ticket previews with about 20 lines of text
Acceptance criteria¶
- AC1: Less text by automated notifications in our team chat room
- AC2: We still have quick access to time-critical notifications with possibility for context related discussions
Suggestions¶
- Consider to move some notifications to a separate channel, e.g. unreviewed progress tickets
- Move github notifications to separate channel as those are not alerts and most often not urgent
- Review which progress ticket queries we use to forward information into our channels. Only keep the exceptional ticket updates in the channel, e.g. urgent or immediate ticket
- Look into making messages more concise, at best only one line for each
- Look into "turn off link preview" in Slack
https://slack.com/help/articles/204399343-Share-links-and-set-preview-preferences#turn-off-link-previews
Related issues
1 (1 open — 0 closed)
- Priority changed from Normal to Low
- Subject changed from Refined use of team-qa-tools Slack channel for automatic notifications to Refined use of team-qa-tools Slack channel for automatic notifications size:S
- Description updated (diff)
- Status changed from New to Workable
- Copied to action #179275: Refined use of team-qa-tools Slack channel for automatic notifications - "Unreview issue" Slack messages size:S added
- Parent task set to #174442
- Status changed from Workable to In Progress
- Assignee set to tinita
I created a channel #team-qa-tools-notifications and added the following subscriptions:
/github subscribe os-autoinst/openQA issues pulls commits discussions
/github subscribe os-autoinst/os-autoinst issues pulls commits discussions
/github subscribe os-autoinst/os-autoinst-common issues pulls commits discussions
/github subscribe os-autoinst/scripts issues pulls commits discussions
/github subscribe os-autoinst/openqa_review issues pulls commits discussions
/github subscribe openSUSE/qem-bot issues pulls commits discussions
/github subscribe openSUSE/qem-dashboard issues pulls commits discussions
/github subscribe openSUSE/Mojo-IOLoop-ReadWriteProcess issues pulls commits discussions
Removed the following from the team channel:
/github unsubscribe openSUSE/qem-bot
/github unsubscribe os-autoinst/openQA
/github unsubscribe os-autoinst/openqa_review
/github unsubscribe os-autoinst/os-autoinst
/github unsubscribe os-autoinst/os-autoinst-common
/github unsubscribe os-autoinst/scripts
I removed the following feeds from our team channel:
The following three are still there:
- Status changed from In Progress to Feedback
I couldn't find out how to make RSS feed messages smaller, it seems the app is not customizable.
Waiting for feedback.
Should the unreviewed issues thing also go to the new channel?
tinita wrote in #note-9:
Should the unreviewed issues thing also go to the new channel?
Those are also prone to causing many redundant messengers and contributes to a lot of noise in the channel.
I like that you kept backlog updates. Those are more concise.
Kinda thinking something like "3 unreviewed issues pending, click here" might be something for the team channel.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF