action #111066
Updated by mkittler over 2 years ago
## Motivation Within #91914 we have implemented notifications which can be configured per job group. Together with multiple other features teams can define their testing scope within job groups and review test results within their scope accordingly. So far we describe individual features within openQA documentation. We should extend the openQA documentation to explain the motivation and how to build a process around job groups. ## Acceptance criteria * **AC1:** The openQA documentation covers how multiple teams can efficiently work together with openQA * **AC2:** Power users have been invited for feedback on the new guide ## Suggestions * A simple and small explanation in the openQA documentation is better than no documentation. So just describe how job groups can be used for teams and what current features relate to that * Consider upstreaming information from https://wiki.suse.net/index.php/RD-OPS_QA/openQA_review#Workflow_for_SLES,_SLED_and_HA_as_an_example https://wiki.suse.net/index.php/RD-OPS_QA/openQA_review and https://confluence.suse.com/display/openqa/QEM+openQA+review+guide to the upstream openQA documentation * Bonus: Remove redundant internal docs afterwards and link to external references