action #116545
Updated by tinita over 1 year ago
## Motivation Same as in other processes https://progress.opensuse.org/projects/openqatests/wiki#SLOs-service-level-objectives is followed better if there are automations that ensure the process, remind about missed targets, etc. ## Acceptance criteria * **AC1:** SLOs are ensured with automation (only a single first (including first+second reminder) ## Suggestions * 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 * 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 * 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#change-552298 * Only write the same comment once or even better follow the SLO about the suggestion of the "second reminder"