Skip to content

BillAnastasiadis/qe-c-backlog-assistant

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

63 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

QE-C Backlog Status

Latest Run: 2024-12-05 01:38:41 GMT (Please refresh to see latest results)

This is the dashboard for Quality Engineering for Containers and Public Cloud.

We are currently working on four projects: Containers, JeOS, WSL, Public Cloud and SLE Micro

General team overview

Bugs vs Features Backlog Length

This table compares the number of bugs against the planned tickets.

Project Bugs Features Total
Containers 1 (1%) 69 (99%) 70
Public Cloud 1 (2%) 44 (98%) 45
SLE Micro 0 (0%) 1 (100%) 1

Incoming vs outcoming during the last 30 days

This table shows the balance between ticket creation and ticket resolution. If more tickets arrive than we are capable of solving, it means that the length of the backlog will grow, and therefore we need more work force in that project. And more tickets come out than come in, so we can divert workforce to other projects if necessary. Two time ranges are contemplated, short-term (30 days) and medium-term (4 months)

Backlog Query New tickets Finished tickets Backlog length Status
Containers 24 38 70 πŸ’š
JeOS 0 0 0 πŸ’š
WSL 0 0 0 πŸ’š
Public Cloud 13 8 45 πŸ”΄
SLE Micro 0 0 1 πŸ’š

Incoming vs outcoming during the last 4 months

Backlog Query New tickets Finished tickets Backlog length Status
Containers 86 95 70 πŸ’š
JeOS 0 0 0 πŸ’š
WSL 0 0 0 πŸ’š
Public Cloud 43 43 45 πŸ’š
SLE Micro 3 4 1 πŸ’š

Backlog Lengths by priority

These tables show the backlog length per priority. The "Warning level" is a the max number of tickets that we consider safe. This level is established by consensus in the team.

Containers

Backlog Query Number of issues Warning level Status
Urgent Priority Length: Containers 0 1 πŸ’š
High Priority Length: Containers 4 3 πŸ”΄
Normal Priority Length: Containers 15 20 πŸ’š

JeOS

Backlog Query Number of issues Warning level Status
Urgent Priority Length: JeOS 0 1 πŸ’š
High Priority Length: JeOS 0 3 πŸ’š
Normal Priority Length: JeOS 0 20 πŸ’š

WSL

Backlog Query Number of issues Warning level Status
Urgent Priority Length: WSL 0 1 πŸ’š
High Priority Length: WSL 0 3 πŸ’š
Normal Priority Length: WSL 0 20 πŸ’š

SLE Micro

Backlog Query Number of issues Warning level Status
Urgent Priority Length: SLE Micro 0 1 πŸ’š
High Priority Length: SLE Micro 0 3 πŸ’š
Normal Priority Length: SLE Micro 0 20 πŸ’š

Public Cloud

Backlog Query Number of issues Warning level Status
Urgent Priority Length: Public Cloud 0 1 πŸ’š
High Priority Length: Public Cloud 3 3 πŸ’š
Normal Priority Length: Public Cloud 14 20 πŸ’š

Pickup time alerts

These tables show the tickets that are in violation of the SLO

Urgent Priority

Backlog Query Number of issues Status
Urgent Priority: Containers 0 πŸ’š
Urgent Priority: JeOS 0 πŸ’š
Urgent Priority: SLE Micro 0 πŸ’š
Urgent Priority: WSL 0 πŸ’š
Urgent Priority: Public Cloud 0 πŸ’š

High Priority

Backlog Query Number of issues Status
High Priority: Containers 2 πŸ”΄
High Priority: JeOS 0 πŸ’š
High Priority: SLE Micro 0 πŸ’š
High Priority: WSL 0 πŸ’š
High Priority: Public Cloud 0 πŸ’š

Normal Priority

Backlog Query Number of issues Status
Normal Priority: Containers 3 πŸ”΄
Normal Priority: JeOS 0 πŸ’š
Normal Priority: SLE Micro 0 πŸ’š
Normal Priority: WSL 0 πŸ’š
Normal Priority: Public Cloud 4 πŸ”΄

Non updated tickets for 15 days

These tables show the tickets that have more than 15 days without any update

Tickets in progress with no changes in 15 days

These tickets are in progress and we should review that because maybe have blockers or are under feedback and we forgot to update the status of the ticket.

Backlog Query Number of issues Status
Not Changed: Containers 9 πŸ”΄
Not Changed: JeOS 0 πŸ’š
Not Changed: SLE Micro 0 πŸ’š
Not Changed: WSL 0 πŸ’š
Not Changed: Public Cloud 5 πŸ”΄

Tickets with the status Blocked and Feedback with no changes in 15 days

These tickets are in progress and we should review that because maybe what is blocking is solved. Or we need to insist when we don't have feedback.

Backlog Query Number of issues Status
Not Changed: Containers (Blocked and Feedback) 6 πŸ”΄
Not Changed: JeOS (Blocked and Feedback) 0 πŸ’š
Not Changed: SLE Micro (Blocked and Feedback) 0 πŸ’š
Not Changed: WSL (Blocked and Feedback) 0 πŸ’š
Not Changed: Public Cloud (Blocked and Feedback) 8 πŸ”΄

Abnormalities

These tickets has some kind of abnormality, and should be alerted to the team and reviewed

In Progress But Not Assigned

These are the typical tickets that due to forgetfulness are in progress but there is no assigned person. If there is any clarification to be made with the person who is working with it, we need to know his name

Backlog Query Number of issues Status
Not Assigned: Containers 0 πŸ’š
Not Assigned: JeOS 0 πŸ’š
Not Assigned: SLE Micro 0 πŸ’š
Not Assigned: WSL 0 πŸ’š
Not Assigned: Public Cloud 0 πŸ’š

Assigned but not started

Some tickets could be blocked by a teammate for a time assigned to him but not started. This option is considered, but care must be taken if too much time has passed or if the person is on sick leave or on vacation. This would mean that the task is effectively blocked

Backlog Query Number of issues Status
Assigned but not started: Containers 2 πŸ”΄
Assigned but not started: JeOS 0 πŸ’š
Assigned but not started: SLE Micro 0 πŸ’š
Assigned but not started: WSL 0 πŸ’š
Assigned but not started: Public Cloud 1 πŸ”΄

New tickets

New tickets that are not workable and need clarification should be reviewed during the refinement meeting.

Backlog Query Number of issues Status
New: Containers 10 πŸ‘ˆ
New: JeOS 0
New: SLE Micro 1 πŸ‘ˆ
New: WSL 0
New: Public Cloud 1 πŸ‘ˆ

Coordination without subtasks

Epics can be defined to record a new line of work in a project. Initially these epics may not have tasks assigned to them. This table is a reminder for the PO

Backlog Query Number of issues Status
Coordination with no subtasks: Containers 0 πŸ’š
Coordination with no subtasks: JeOS 0 πŸ’š
Coordination with no subtasks: SLE Micro 0 πŸ’š
Coordination with no subtasks: WSL 0 πŸ’š
Coordination with no subtasks: Public Cloud 0 πŸ’š

Epics

Container Epics

Epic Status Start Date Progress
{SLE-Micro} Establish ppc64 test runs for SLEM6 New 2024-06-21 75%
{SLE-Micro} Fixing SLE-Micro 6.1 New 2024-07-08 100%
BCI image stat collection New 2024-04-23 0%
{containers} FIPS mode New 2023-09-19 100%
{WSL} Improvement of the installation processes New 2023-10-17 0%
{containers} BCI Testing on IBM Hyper Protect Plat... Workable 2024-07-03 50%
{WSL} WSL Documentation New 2022-09-21 0%
{containers} BCI testing on OpenShift Workable 2022-03-01 80%
{MinimalVM} MinimalVM Cloud image test automation Workable 2020-04-29 70%
{WSL} Backend improvement to create tests for WSL2 New 2019-11-27 100%
{MinimalVM} separate hyperv from svirt backend New 2021-07-13 0%

JeOS Epics

No active epics for this project

SLE Micro Epics

No active epics for this project

WSL Epics

No active epics for this project

Public Cloud Epics

Epic Status Start Date Progress
cloud-init test coverage Blocked 2024-07-14 66%
Test staging images Workable 2022-02-21 0%

Aging of tickets

Mesures the time since the ticket is created and the ticket is resolved

Aging tickets finished in the last 30 days

Backlog Query Days to complete (Adv) Days to complete (Median) Days to complete (Std deviation)
Containers 91 21 45
Public Cloud 24 36 3

Other links

Finished tickets this week

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages