action #116605
Updated by okurz over 1 year ago
## Motivation #114983#note-15 received a false notice from slo-gin within one day when for a "Low" ticket the update should have happened only after 365 days https://github.com/openSUSE/backlogger contains the source code and maybe https://github.com/openSUSE/openqa-tests-backlog is the configuration, it would be nice to have both of them documented somewhere. I managed to retrieve the action run associated with the mentioned comment: https://github.com/openSUSE/openqa-tests-backlog/actions/runs/3066942771/jobs/4952687708 The issue in question was commented during evaluation query for 'Within due-date (10 days)'; the last comment in #114983 did not extend the due date, so the ticket was still more that 10 days after the limit and as the last comment was not from slo-gin, the ticket was returned for the query and commented. In this case, the text of the comment is misleading, as it is commented not because of SLO period, but because of the due-date being larger than 10 days. Further clarification is needed, if we want this behavior and possibly extend the configuration to also set a custom message instead of hard-coded comment For due-date exceeded I suggest to have a custom message. If this is not so easy to do then for now I suggest to disable any commenting on due-date exceeded tickets ## Acceptance criteria * **AC1:** Tickets with priority "Low" do not receive comments about SLO periods exceeded ## Suggestions * Review the new project https://github.com/openSUSE/backlogger and learn how to contribute to it * Put the custom message from https://github.com/openSUSE/backlogger/blob/main/backlogger.py#L57 into the configuration, e.g. https://github.com/openSUSE/openqa-tests-backlog/blob/main/queries.yaml#L25 and read that from backlogger.py instead of the hardcoded one * Alternative: Just remove due-date related updating of tickets for now