QA

Motivation¶

Some tickets don't see regular updates, even with automated reminders in some cases. See https://progress.opensuse.org/projects/openqatests/wiki#SLOs-service-level-objectives for the documented workflows/goals. We assume processes are followed better if there is automation that reminds people about missed targets and makes it easier to understand what updates are missing.

Acceptance criteria¶

• AC1: DONE SLOs are reflected in automated reminders
• AC2: DONE The first reminder is implemented based on the documented workflow
• AC3: The second reminder is known to update the priority automatically

Suggestions¶

• DONE: Wait for #116545
• DONE: Same as in queries for QA tools we likely should only look at the update time of tickets with no subtasks, e.g. see the definition of https://progress.opensuse.org/issues?query_id=542, to prevent cases like https://progress.opensuse.org/issues/113749#note-13 ff which is Urgent but hasn't been updated for a long time.
• DONE: Only write the same comment once -> #116545
• Research what has been done in #113797
• Review and understand https://github.com/openSUSE/openqa-tests-backlog as well as https://github.com/openSUSE/backlogger and https://opensuse.github.io/openqa-tests-backlog/
• As the queries in https://github.com/openSUSE/openqa-tests-backlog/blob/main/queries.yaml#L5 are not named queries but defined in place we could just define a "grace period" for each query and only act automatically if not done already by users, e.g. don't remind on urgent tickets after 7 days but only 7+2 days
• Follow the SLO about the suggestion of the "second reminder"