Project

General

Profile

action #116605

False SLO update comment for a Low ticket size:M

Added by okurz 2 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
Start date:
2022-09-15
Due date:
% Done:

0%

Estimated time:

Description

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


Related issues

Related to QA - action #116545: Automated alerts and reminders about SLO's for openqatests (only one reminder) size:MResolved

History

#2 Updated by okurz 2 months ago

  • Description updated (diff)

#3 Updated by jbaier_cz 2 months ago

I am missing information like what is slo-gin and where is it running from? I supose 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

#4 Updated by okurz 2 months ago

Good that you could investigate and understand this. 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

#5 Updated by okurz 2 months ago

  • Subject changed from False SLO update comment for a Low ticket to False SLO update comment for a Low ticket size:M
  • Description updated (diff)
  • Status changed from New to Workable

#6 Updated by okurz 2 months ago

  • Related to action #116545: Automated alerts and reminders about SLO's for openqatests (only one reminder) size:M added

#7 Updated by jbaier_cz 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to jbaier_cz

I will try to handle this by introducing the custom message into the configuration.

#8 Updated by jbaier_cz 2 months ago

Proposal for new configuration is in https://github.com/openSUSE/openqa-tests-backlog/pull/4

#9 Updated by jbaier_cz 2 months ago

  • Status changed from In Progress to Feedback

And the feature should be implemented in https://github.com/openSUSE/backlogger/pull/6

#10 Updated by jbaier_cz about 2 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF