Project

General

Profile

Actions

action #104199

closed

Prevent confusion when openQA comments look like both a bugref as well as label at the same time size:M

Added by okurz almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-12-20
Due date:
% Done:

0%

Estimated time:

Description

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 the user to not create ambiguous "label + bugref" comments
  • 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


Related issues 1 (0 open1 closed)

Copied to openQA Project (public) - action #104616: Make openQA labels clearly visibleResolvedkraih2021-12-20

Actions
Actions

Also available in: Atom PDF