QA » openQA Project

Hi, thank you for reporting this neat idea.

The current parsing of openQA job settings and triggering is done in https://github.com/os-autoinst/scripts/blob/master/openqa-trigger-bisect-jobs. If we would want to parse the package name from qem-dashboard or smelt we could do it in that script. But as alternative we can consider to read out package names already when triggering openQA jobs in qem-bot which already parses such data. So we could forward the id:package relation in job settings even though openQA jobs don't strictly need it and then only access such information when triggering those SLE maintenance investigation bisect jobs.

The idea of the ticket is valid but the scope of users benefitting from that is low in comparison and rather low RoI so prioritizing as "Low" accordingly and in "future". Please reach out to me if you think we should consider.