Project

General

Profile

coordination #69310

Updated by okurz 2 months ago

## Motivation
We want to follow the https://progress.opensuse.org/projects/openqav3/wiki#ticket-workflow including https://progress.opensuse.org/projects/qa/wiki#How-we-work-on-our-backlog which define some SLOs for ourselves which are hard and tedious to track as humans but bots would be happy to do that job.

## Ideas

* DONE: ~~Query Query Redmine via GitLab CI bot to update due date: On GitHub we have bots checking that certain parameters are met, such as stale PRs or conflicts. It would be great to update the Due Date automatically according to tickets that need updates, taking priority into account, which then allow Redmine to send out notifications. As an alternative write comments directly.~~
* Remove due-date on resolved tickets again to prevent reminders on still open parents when resolved subtasks have due-dates in the past but all open tasks do not yet have due-dates
* Have a GHA CI job that fails whenever any target number or SLO is not met, e.g. one check for each query in https://progress.opensuse.org/projects/qa/wiki#Target-numbers-or-guideline-should-be-in-priorities
directly.

Back