Project

General

Profile

Actions

action #137831

closed

Reduce limit on feedback tickets to 10

Added by tinita 6 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Organisational
Target version:
Start date:
2023-10-12
Due date:
% Done:

0%

Estimated time:

Description

Observation

See #136007


Related issues 1 (0 open1 closed)

Copied from openQA Infrastructure - action #136007: Conduct "lessons learned" with Five Why analysis for network protocols failures on multimachine tests on HA/SAP size:SResolvedtinita

Actions
Actions #1

Updated by tinita 6 months ago

  • Copied from action #136007: Conduct "lessons learned" with Five Why analysis for network protocols failures on multimachine tests on HA/SAP size:S added
Actions #2

Updated by okurz 6 months ago

Our current query in https://github.com/os-autoinst/qa-tools-backlog-assistant/blob/520bee381b84aaf6e2ade49aaa4eaf6da104a947/queries.yaml#L42 just counts all tickets in feedback, not only low or something. Right I have 13 tickets in feedback, all legitimately waiting for others. Maybe we should distinguish on "not-low", maybe just reduce to 15? Maybe just more rigid checking on getting stuff done?

Actions #3

Updated by okurz 6 months ago

  • Assignee set to okurz
Actions #4

Updated by okurz 6 months ago

  • Status changed from New to In Progress

We discussed this in the retro. As there were more than 10 tickets but all for legitimate reason we tried to find different solutions. First we thought we could move tickets for which we don't expect feedback soon to "Next" but our feedback query https://progress.opensuse.org/issues?query_id=520 is looking on tickets assigned to team members regardless of target version. So instead we opted to change the query to only look at not-low tickets which is giving us yet another use case where it makes sense to reduce the prio of a ticket to low.

And to reduce the alert limit
https://github.com/os-autoinst/qa-tools-backlog-assistant/pull/38

Actions #5

Updated by okurz 6 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF