action #178897
closedRefined use of team-qa-tools Slack channel for automatic notifications size:S
0%
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
Updated by okurz 13 days ago
- Copied to action #179275: Refined use of team-qa-tools Slack channel for automatic notifications - "Unreview issue" Slack messages size:S added
Updated by tinita 1 day ago ยท Edited
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
Updated by tinita 1 day ago
I removed the following feeds from our team channel:
- https://progress.opensuse.org/issues?query_id=545
- https://progress.opensuse.org/issues?query_id=544
- https://progress.opensuse.org/issues?query_id=230
- https://progress.opensuse.org/issues?query_id=481
- https://progress.opensuse.org/projects/qa/issues?query_id=576
The following three are still there:
- https://progress.opensuse.org/issues?query_id=543 SLO urgent
- https://progress.opensuse.org/issues?query_id=542 SLO immediate
- https://progress.opensuse.org/issues?query_id=514 exceeding due-date
Updated by livdywan 1 day ago
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.
Updated by okurz 1 day ago
I removed the following feeds from our team channel:
https://progress.opensuse.org/issues?query_id=545
https://progress.opensuse.org/issues?query_id=544
https://progress.opensuse.org/issues?query_id=230
https://progress.opensuse.org/issues?query_id=481
https://progress.opensuse.org/projects/qa/issues?query_id=576
those were helpful so should be somewhere. If you don't want to have them in your new room maybe yet another room for those?
tinita wrote in #note-9:
Should the unreviewed issues thing also go to the new channel?
"unreviewed issues" often point to unexpected time-critical regressions hence should stay in our usual channel. Would be nice if we can make them more concise as Liv suggested but I guess that would be a separate feature request.
Updated by tinita about 4 hours ago
- Status changed from Feedback to Resolved
I added the link to the new room here: https://progress.opensuse.org/projects/qa/wiki/Tools#Common-tasks-for-team-members
As discussed in the meeting today, we are fine now. The removed progress feeds are covered by our backlog status app.
I added all team members to the new channel.