Project

General

Profile

Actions

action #154261

closed

QA - coordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release

QA - coordination #153928: [epic] Ideas from SUSE QE Tools workshop 2024-01-19 Filter openQA todo-jobs on /tests belonging to groups, review teams, etc

[spike][timeboxed:20h] batch commenting on all openQA jobs, e.g. involving a specified SLE maintenance incident in webUI size:M

Added by okurz 3 months ago. Updated 27 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
2024-03-27
% Done:

0%

Estimated time:

Description

Motivation

As proposed by szarate from a personal discussion between okurz and szarate 2024-01-25: When reviewing SLE maintenance tests openQA test failures failing for the same reason can be encountered which one wants to comment or label with the same content. To make such feature easily accessible it should be discoverable over the webUI.

Goals

  • G1: openQA jobs as filtered on the webUI, e.g. from /tests or /tests/overview, can be commented with the same text in one action

Suggestions


Related issues 3 (2 open1 closed)

Related to openQA Project - action #120118: Provide job settings filter optionsNew2022-11-08

Actions
Related to openQA Project - coordination #154768: [saga][ux] State-of-art user experience for openQANew2023-10-26

Actions
Related to openQA Project - action #157543: [sporadic] ci openQA: t/ui/23-audit-log.t fails size:MResolvedmkittler2024-03-19

Actions
Actions #1

Updated by okurz 3 months ago

  • Related to action #120118: Provide job settings filter options added
Actions #2

Updated by okurz 3 months ago

  • Related to coordination #153928: [epic] Ideas from SUSE QE Tools workshop 2024-01-19 Filter openQA todo-jobs on /tests belonging to groups, review teams, etc added
Actions #3

Updated by okurz 3 months ago

  • Target version changed from future to Tools - Next
Actions #4

Updated by okurz 3 months ago

  • Parent task set to #153928
Actions #5

Updated by szarate 3 months ago

Actions #6

Updated by szarate 3 months ago

this is one of these cases, where I’d go on openQA, and use the in-webui-label-all, after reviewing the failed tests and being sure that there isn't anything in the failing results from other QE Teams that has a relationship to the particular update.

Also the SUSEConnect from last week situation mentioned in the slack message is another one of these, where said feature would have been useful

Actions #7

Updated by okurz about 2 months ago

  • Target version changed from Tools - Next to Ready
Actions #8

Updated by okurz about 2 months ago

  • Subject changed from [spike][timeboxed:20h] batch commenting on all openQA jobs involving a specified SLE maintenance incident in webUI to [spike][timeboxed:20h] batch commenting on all openQA jobs, e.g. involving a specified SLE maintenance incident in webUI size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions #9

Updated by mkittler about 1 month ago

  • Status changed from Workable to In Progress
  • Assignee set to mkittler
Actions #10

Updated by openqa_review about 1 month ago

  • Due date set to 2024-03-27

Setting due date based on mean cycle time of SUSE QE Tools

Actions #11

Updated by mkittler about 1 month ago

  • Status changed from In Progress to Feedback
Actions #13

Updated by livdywan about 1 month ago

  • Related to action #157543: [sporadic] ci openQA: t/ui/23-audit-log.t fails size:M added
Actions #14

Updated by JERiveraMoya about 1 month ago

Nice feature! could you please provide a refresh after the action is done, I need to press F5 to see the jobs label in batch. Thanks.

Actions #15

Updated by JERiveraMoya about 1 month ago

also for 0 jobs selected would be good to not show the button or if the popup needs to be showed (it is easy to implement that way or something), that you could only cancel, no need for waiting for a weird db message afterward to push the button to send to 0 jobs.

Actions #16

Updated by JERiveraMoya about 1 month ago

one neatpicking one :) why does it sounds to me better "bulk" than "batch" I don't know maybe because I saw in the progress UI, but googling about the different I still not convinced why, just in case someone else had the same feeling, bulk sounds to me like for data to put somewhere when batch more like scripting and operations, that is the only thing I could figure out, but it is not important :)

Actions #17

Updated by mkittler about 1 month ago

  • We could suggest suggest and allow reloading via the flash message shown on success.
  • I guess we could rename it to "Bulk commenting". That would be very easy because the term is only used on the UI (and not in the underlying API and events) because I also didn't like it much. Maybe we can just use "Add comments"?.
  • The case of zero jobs should be improved, indeed (if there's really a DB message showing up).
Actions #19

Updated by mkittler 27 days ago

  • Status changed from Feedback to Resolved

The PR was merged. With that I'd say we can consider this ticket resolved. We can create follow-up tickets for this feature once users ask us to extend it.

Actions

Also available in: Atom PDF