Project

General

Profile

Actions
Copy link

action #135746

closed

Longer term plan along with less confusion for the team with additional "Next" target version size:M

Added by okurz 8 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Low
Assignee:
okurz
Target version:
openQA Project - Ready
Start date:
2023-09-14
Due date:
% Done:

0%

Estimated time:
Tags:
organisational

Description

Motivation

Some stakeholders often like to have a bit longer schedule regarding the plans from the SUSE QE Tools team. On the other hand the team is often overwhelmed with around 100 tickets in the backlog. So I propose next to the "Ready" and "future" target versions to introduce "Next" to be in the middle along with all necessary steps in the process so that we would track tickets in "Next" accordingly as well.

Acceptance criteria

  • AC1: https://progress.opensuse.org/issues/?query_id=230 is ensured to have <=64 tickets
  • AC2: The new "Next" query is ensured to have less than 100 tickets as well
  • AC3: progress.opensuse.org/projects/qa/wiki/tools references the "Ready" and "Next" backlogs with according explanations

Suggestions

Actions
Copy link
 #1

Updated by livdywan 8 months ago

  • Subject changed from Longer term plan along with less confusion for the team with additional "Next" target version to Longer term plan along with less confusion for the team with additional "Next" target version size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #2

Updated by okurz 8 months ago

  • Status changed from Workable to In Progress
  • Assignee set to okurz
Actions
Copy link
 #4

Updated by openqa_review 8 months ago

  • Due date set to 2023-09-29

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #5

Updated by okurz 8 months ago

  • Status changed from In Progress to Feedback

https://github.com/os-autoinst/qa-tools-backlog-assistant/pull/36 merged, status page https://os-autoinst.github.io/qa-tools-backlog-assistant/ shows entries. I updated the team wiki on multiple places and now would like to wait for feedback from the team

Actions
Copy link
 #6

Updated by okurz 8 months ago

  • Due date changed from 2023-09-29 to 2023-11-10
  • Priority changed from High to Low
  • Target version changed from Ready to Tools - Next

We successfully looked at the new queries in the last coordination call and will run the current state over the next weeks and then review how we like it

Actions
Copy link
 #7

Updated by okurz 7 months ago

  • Due date deleted (2023-11-10)
  • Status changed from Feedback to Resolved
  • Target version changed from Tools - Next to Ready

The team is happy with our current approach.

Actions
Copy link

Also available in: Atom PDF