action #154261
closedQA - 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
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¶
- Consider filters like https://openqa.opensuse.org/tests/overview?arch=aarch64&flavor=&machine=&test=&modules=&module_re=&group_glob=¬_group_glob=&comment=&todo=1&distri=opensuse&groupid=1&version=Tumbleweed#
- As we already have a filter box on /tests/overview it might be the easiest to add a batch-comment-field in there. Then write a comment on all jobs currently shown in the filtered list (make it obvious that it is not a comment search field though)
- As alternative consider something like selection boxes with possibility to select all, unselect all, select/unselect individuals
- Consider a confirmation dialog if more than N jobs would be commented
- Consider the audit log and a specific event for the batch action
- See related issues #120118 and #153928
Updated by okurz 3 months ago
- Related to action #120118: Provide job settings filter options added
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
Updated by szarate 3 months ago
- Related to coordination #154768: [saga][ux] State-of-art user experience for openQA added
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
Updated by okurz about 2 months ago
- Target version changed from Tools - Next to Ready
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
Updated by mkittler about 2 months ago
- Status changed from Workable to In Progress
- Assignee set to mkittler
Updated by openqa_review about 2 months ago
- Due date set to 2024-03-27
Setting due date based on mean cycle time of SUSE QE Tools
Updated by mkittler about 2 months ago
- Status changed from In Progress to Feedback
Updated by mkittler about 2 months ago
Updated by livdywan about 1 month ago
- Related to action #157543: [sporadic] ci openQA: t/ui/23-audit-log.t fails size:M added
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.
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.
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 :)
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).
Updated by mkittler about 1 month ago
Updated by mkittler about 1 month 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.