coordination #95857
Updated by ilausuch almost 3 years ago
## Motivation
For QAM incident tests we should consider using flavor rather than build to encode incident+test to ensure that
* "Next & previous" results only show results for the very same incident, not all different kind of packages
* openQA can resolve the real "latest" result per incident on /tests/overview, e.g. to make reports on https://openqa.io.suse.de/openqa-review/ more useful for incident tests as well
* label carry over works for repeated failures within the same incident
## Acceptance criteria
* **AC1:** openQA "Next & previous" for any incident test only shows jobs for the same package
* **AC2:** The test overview link on https://openqa.suse.de/parent_group_overview/8#grouped_by_build shows still results from multiple incidents for multiple product versions at the same time
## Suggestions
* Without changing the build variable we could try to just add the package (maybe also the incident number) to flavor
* To avoid confusion, this is about links that are generated in a previous part but no the webui "next & prev"