action #164490
closed
QA - coordination #164466: [saga][epic] Scale up: Hyper-responsive openQA webUI
coordination #164469: [epic] Better tools team incident handling
[tools] We need to find a way to remind us about the process which we gave ourselves: How about a checklist that could be followed based on what's already mentioned in https://progress.opensuse.org/projects/qa/wiki/Tools#Process ? size:S
Added by okurz about 1 month ago.
Updated 17 days ago.
Category:
Feature requests
Description
Motivation¶
See #163610-4
Acceptance criteria¶
- AC1: A checklist is easily available to us when an incident happens
- AC2: We do remember to actually use the template
- AC3: No duplicate content
Suggestions¶
- Research about a checklist option in Slack that could be easily requested case by case with a slash-command, like `"/tools-checklist" which a Slack bot would respond with a checklist in a thread related to an incident. The checklist could be an excerpt of the wiki page or a separate page we need to move the checklist to, or if nothing else works then just defined within Slack
- If it's not possible to just show a part of our wiki as checklist then consider creating a checklist separately and reference that checklist in the wiki and not duplicate in the wiki
Files
Related issues
2 (2 open — 0 closed)
- Copied from action #164487: [tools] Research about a status page or maintenance fallback mode information page which we could redirect to. That could be known issues on openQA itself as well as redirect on the level of the web proxy added
- Copied to action #164493: [tools] Research the meaning and implications of the number of workers as a tuning parameter. Come up with an understanding on how to select the value, where the limits are, what suggestions to openQA admins are -> add that in openQA documentation added
- Target version changed from future to Ready
- Subject changed from [tools] We need to find a way to remind us about the process which we gave ourselves: How about a checklist that could be followed based on what's already mentioned in https://progress.opensuse.org/projects/qa/wiki/Tools#Process ? to [tools] We need to find a way to remind us about the process which we gave ourselves: How about a checklist that could be followed based on what's already mentioned in https://progress.opensuse.org/projects/qa/wiki/Tools#Process ? size:S
- Description updated (diff)
- Status changed from New to Workable
- Assignee set to ybonatakis
- Status changed from Workable to Feedback
No respond yet from It
Shahryar Ahsan
15 hours ago
Hi
@Ioannis Bonatakis
, Please raise it via Jira and the request will follow the Slack app integration process as approvals are required. Thanks
Seems the inc-checklist needs permission to be accessed. maybe I should recreate it?!
- Status changed from Feedback to Blocked
ybonatakis wrote in #note-13:
SD ticket created https://sd.suse.com/servicedesk/customer/portal/1/SD-164936
We discussed this a bit in the morning. I suggest to clarify if we can use /canvas as-is, or how the Slack "app" adding /checklist-incidents would look as that still needs to be implemented and deployed somewhere (e.g. GitHub workflow, GitLab pipeline, or somewhere else)
- Status changed from Blocked to Feedback
@ybonatakis I would appreciate at least a suggestion on how the Slack "app" would look. Not saying to implement it, but what would be required and what will we get out of it compared to /canvas or using a Slack workflow.
We tried out different suggestions. My favorite approach is to create a workflow that when adding a :rotating_light: emoji reaction to a message sends a list with content
1. task force
2. report ticket
3. inform users
4. apply mitigations
5. keep it running
6. fix cause
An workflow as described by Oli created.
I havent removed the bookmarks just yet. Feel free to delete them if they are not of any use.
Before that, I tried hard to create an app in Slack in a personal instance but I faced many issues which slow down the process.
I am not sure if the job is done here, but if it is ok I will resolve the ticket
ybonatakis wrote in #note-17:
I havent removed the bookmarks just yet. Feel free to delete them if they are not of any use.
I guess inc-checklist2 is a test workflow that should be deleted?
I am not sure if the job is done here, but if it is ok I will resolve the ticket
I'd say to fulfill AC2 this should be documented in the wiki, meaning 1) how to use the workflow and 2) an onboarding step to cover giving every team member access to the workflow
livdywan wrote in #note-18:
ybonatakis wrote in #note-17:
I havent removed the bookmarks just yet. Feel free to delete them if they are not of any use.
I guess inc-checklist2 is a test workflow that should be deleted?
Someone has already deleted
I am not sure if the job is done here, but if it is ok I will resolve the ticket
I'd say to fulfill AC2 this should be documented in the wiki, meaning 1) how to use the workflow and 2) an onboarding step to cover giving every team member access to the workflow
- done
- I think I gave access to all of the Qatoolers
In case another checklist is constructed.
- go to #team-qa-tools
- Integrations > Add Automation > Workflows > Create a Workflow
- click top left to enter a title
- Choose an event > When an emoji reaction is used.
4.1 choose an emoji and give #team-qa-tools in the Channels
- Add another Action > Messages > Reply to a message in thread
- Status changed from Feedback to Resolved
I believe with the discussion in the morning we are good with this and we are moving on. closing
Also available in: Atom
PDF