action #104199
Updated by okurz over 2 years ago
## Motivation See #95479#note-42 . If for example someone writes in an openQA comment `label:force_result:passed:bsc#1234` then openQA does *not* detect this as a label but always as a bugref. So a bugref always *wins* over a label but this is not obvious to users ## Acceptance criteria * **AC1:** openQA guides prevents the user to not create creation of ambiguous "label + bugref" comments * **AC2:** "ticket reference URLs" are still expanded in label description strings * **AC3:** Any text starting with "label:" is not detected as an openQA bugref ## Examples * If user writes a comment with `bsc#1234` then this is parsed as bugref, expanded into a proper `a href` pointing to bugzilla.suse.com/…, openQA shows the bug icon and carries over the bug if jobs in the same scenario fail in the same way. * user writes `label:force_result:softfailed:known_issue42` which changes the result of a job to "softfailed". openQA shows the "label" icon, no carry over happening * User wants to create a comment with *both* a bugref and a label, e.g. ``` * module 1: bsc#1234 * module 2: label:ignore ``` * Desired behaviour, not currently working as expected: user wants to use a label and force the result of a *single* job (no carry over intended) but still wants to provide a proper link to a bug, e.g. again `bsc#1234` which would properly extended * https://openqa.opensuse.org/tests/2118438#comments shows how multiple comments can include multiple bugrefs ## Out of scope Different visual representation of labels, see #104616