Project

General

Profile

Actions

action #123451

closed

[retro] Open questions on how a ticket about update_install on PowerPC was handled size:M

Added by livdywan almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Organisational
Target version:
Start date:
2023-01-20
Due date:
2023-02-07
% Done:

0%

Estimated time:

Description

Motivation

In retrospect we're not clear why #115793 seems to have received as little attention as it did.

Acceptance criteria

  • AC1: Existing team processes better handle tickets nearing SLO's

Observation

  • The ticket was filed under openQA Tests
  • The ticket was moved between [core] and [tools] during its lifetime.
  • The ticket was moved between Feedback and Workable
  • There were updates close to our SLO's meaning it could have been overlooked when using queries such as update forecast.
    • Part of the SM workflow is checking this query. If it did come up there's no record of it.
  • There was some unclarity as to the nature of the issue. Comments don't reveal what may have been discussed e.g. in Slack, Daily or Unlock calls.
  • There's an unexplained a gap of > 1 month between updates.

Suggestions

  • Cover least recently updated tickets in Unblock calls
  • Try out a dedicated new query like tickets updated by priority
  • Find other examples of tickets that couldn't be handled better where we might have more information on what happened

Related issues 1 (0 open1 closed)

Copied from openQA Tests (public) - action #115793: [qe-core] test fails in update_install on PowerPC size:MRejected

Actions
Actions

Also available in: Atom PDF