Project

General

Profile

Actions
Copy link

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.

Status:
Resolved
Priority:
Normal
Assignee:
ybonatakis
Category:
Feature requests
Target version:
openQA Project - Ready
Start date:
2024-07-26
Due date:
% Done:

0%

Estimated time:

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

clipboard-202408060810-6bj7r.png (39.2 KB) clipboard-202408060810-6bj7r.png ybonatakis, 2024-08-06 06:10

Related issues 2 (2 open — 0 closed)

Copied from openQA Infrastructure - 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 proxyNew2024-07-26

Actions
Copied to openQA Infrastructure - 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 documentationNew2024-07-26

Actions
Actions
Copy link
 #1

Updated by okurz about 1 month ago

  • 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
Actions
Copy link
 #2

Updated by okurz about 1 month ago

  • 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
Actions
Copy link
 #3

Updated by okurz about 1 month ago

  • Target version changed from future to Ready
Actions
Copy link
 #4

Updated by okurz about 1 month ago

  • Tags deleted (infra)
Actions
Copy link
 #5

Updated by okurz about 1 month ago

  • 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
Actions
Copy link
 #6

Updated by ybonatakis about 1 month ago

  • Assignee set to ybonatakis
Actions
Copy link
 #7

Updated by ybonatakis 29 days ago

I created a new command https://api.slack.com/apps/A07G01YGP2L /checklist-incidents. To continue I need to install the app. Which I requested https://suse.slack.com/archives/D02D0U99RQB/p1722629216342619

Actions
Copy link
 #8

Updated by ybonatakis 27 days ago

I have added a bookmark in the #team-qa-tools to the https://progress.opensuse.org/projects/qa/wiki/Tools#Process for now. I hope this is ok

Actions
Copy link
 #9

Updated by ybonatakis 27 days ago

  • Status changed from Workable to Feedback

Added another bookmark which should open a checklist -> https://app.slack.com/client/T02863RC2AC?cdn_fallback=2
this document is created by /canvas. there are also some templates for richer experience

Actions
Copy link
 #10

Updated by ybonatakis 26 days ago

No respond yet from It

Actions
Copy link
 #11

Updated by ybonatakis 25 days ago

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

Actions
Copy link
 #12

Updated by ybonatakis 25 days ago

Seems the inc-checklist needs permission to be accessed. maybe I should recreate it?!

Actions
Copy link
 #13

Updated by ybonatakis 25 days ago

  • Status changed from Feedback to Blocked
Actions
Copy link
 #14

Updated by livdywan 23 days ago

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)

Actions
Copy link
 #15

Updated by livdywan 23 days ago

  • 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.

Actions
Copy link
 #16

Updated by okurz 20 days ago

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
Actions
Copy link
 #17

Updated by ybonatakis 19 days ago

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

Actions
Copy link
 #18

Updated by livdywan 19 days ago

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

Actions
Copy link
 #19

Updated by ybonatakis 19 days ago

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

  1. done
  2. I think I gave access to all of the Qatoolers
Actions
Copy link
 #20

Updated by ybonatakis 19 days ago

In case another checklist is constructed.

  1. go to #team-qa-tools
  2. Integrations > Add Automation > Workflows > Create a Workflow
  3. click top left to enter a title
  4. Choose an event > When an emoji reaction is used. 4.1 choose an emoji and give #team-qa-tools in the Channels
  5. Add another Action > Messages > Reply to a message in thread
Actions
Copy link
 #21

Updated by ybonatakis 17 days ago

Can we resolve this?

Actions
Copy link
 #22

Updated by ybonatakis 17 days ago

  • 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

Actions
Copy link

Also available in: Atom PDF