action #61985

Clarification of "openqa" and "infra" queues in

Added by okurz 6 months ago. Updated 6 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Current State

Last year we had some tickets in the "openqa" queue, which is covered by the SLA between QA SLE and EngInfra, and some tickets in "infra". Experiences:

  • + Tickets in the "infra" queue were being worked on faster than in previous years
  • - tickets in "openqa" were sometimes neglected for longer times
  • - EngInfra-members did not understand what the "openqa" queue is for or did not know of the SLA
  • - it is not possible to reply on tickets in "openqa" queue

Further details


#1 Updated by okurz 6 months ago

mmaher, mawerner, okurz talked:

  • mmaher thought we use the "openqa" queue also team-internally, e.g. within QA, to organize work. I don't think this is the case
  • mmaher is the only one that would look into openqa queue -> likely to hit times when mmaher is not available

Our suggestions:

  1. Do not use openqa queue
  2. Disable/delete openqa queue to prevent further confusion (this should not be seen as invalidation for the SLA)
  3. Make everyone within EngInfra aware of the SLA existance and its requirements which are currently anyway implicitly fulfilled by the better work on the normal infra queue

@nsinger do you agree?

#2 Updated by okurz 6 months ago

In the personal talk mmaher also suggested to open a ticket about that. I already had that with , it was closed suggesting to talk personally so we are going in circles.

#3 Updated by okurz 6 months ago

  • Description updated (diff)

#4 Updated by okurz 6 months ago

Had a discussion with Evzenie Sujskaja trying to crosscheck mutual expectations, current state and plans. She learned from me that tickets in by default are not public. Workaround: Put others (even potentially mailing lists) in CC. A new system, potentially based on Jira ServiceDesk is planned. Forwarded SLA to Evzenie as she did not know about it or find it anywhere. The discussion backed by suggestion to not use the openqa ticket queue at all. Evzenie also stated that ARM hardware is managed solely by the architecture team which contradicts the SLA as well.

#5 Updated by okurz 6 months ago

  • Status changed from New to Resolved
  • Assignee set to okurz
  • Target version set to Done

Discussed with runger. He will introduce himself to Evzenie and talk about the SLA, how it should be applied, updated, etc.

Updated with the recommendation to not use the "openqa" queue. I guess this is all what can be reached with reasonable effort hence closing.

Also available in: Atom PDF