Latest Run: 2026-03-15 23:54:18 GMT (Please refresh to see latest results)
This is the dashboard for Quality Engineering for Containers, Images and Public Cloud.
We are currently working on four projects: Containers & Images and Public Cloud
- General team overview
- Backlog Lengths by priority
- Pickup time alerts
- Non updated tickets for 15 days
- No Changes in 15 Days (Blocked and Feedback)
- Abnormalities
- Epics
Bugs vs Features Backlog Length
This table compares the number of bugs against the planned tickets.
| Project | Bugs | Features | Total |
|---|---|---|---|
| Containers & Images | 0 (0%) | 102 (100%) | 102 |
| Public Cloud | 0 | 0 | 0 |
Incoming vs outcoming during the last 4 months
| Backlog Query | New tickets | Finished tickets | Backlog length | Status |
|---|---|---|---|---|
| Containers | 129 | 148 | 102 | π |
| Public Cloud | 0 | 0 | 0 | π |
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.
| Backlog Query | Number of issues | Warning level | Status |
|---|---|---|---|
| Urgent Priority Length: Containers & Images | 0 | 1 | π |
| High Priority Length: Containers & Images | 5 | 3 | π΄ |
| Normal Priority Length: Containers & Images | 6 | 20 | π |
| Backlog Query | Number of issues | Warning level | Status |
|---|---|---|---|
| Urgent Priority Length: Public Cloud | 0 | 1 | π |
| High Priority Length: Public Cloud | 0 | 3 | π |
| Normal Priority Length: Public Cloud | 0 | 20 | π |
These tables show the tickets that are in violation of the SLO
| Backlog Query | Number of issues | Status |
|---|---|---|
| Urgent Priority: Containers & Images | 0 | π |
| Urgent Priority: Public Cloud | 0 | π |
| Backlog Query | Number of issues | Status |
|---|---|---|
| High Priority: Containers & Images | 2 | π΄ |
| High Priority: Public Cloud | 0 | π |
| Normal Priority: Public Cloud | 0 | π
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 & Images | 7 | π΄ |
| Not Changed: Public Cloud | 0 | π |
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 & Images (Blocked and Feedback) | 13 | π΄ |
| Not Changed: Public Cloud (Blocked and Feedback) | 0 | π |
These tickets has some kind of abnormality, and should be alerted to the team and reviewed
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 & Images | 0 | π |
| Not Assigned: Public Cloud | 0 | π |
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 & Images | 9 | π΄ |
| Assigned but not started: Public Cloud | 0 | π |
New tickets that are not workable and need clarification should be reviewed during the refinement meeting.
| Backlog Query | Number of issues | Status |
|---|---|---|
| New: Containers & Images | 47 | π |
| New: Public Cloud | 0 |
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 & Images | 0 | π |
| Coordination with no subtasks: Public Cloud | 0 | π |
| Epic | Status | Start Date | Progress |
|---|---|---|---|
| Testing of the SLES 16.1 transactional mode | New | 2026-01-22 | 66% |
| {Publiccloud} Azure AITL/LISA testing | New | 2024-10-17 | 66% |
| {Publiccloud} Establish disaster recover for larry... | New | 2025-11-06 | 50% |
| SLES 16 Maintenance for QE-C | New | 2025-08-06 | 88% |
| Infrastructure monitoring project | New | 2024-10-24 | 90% |
| {retro} Instable tests, avoid repetitive workload | New | 2025-07-30 | 0% |
| {retro} PR Management | New | 2025-07-30 | 0% |
| {PublicCloud} Knowledge democratization of the Pub... | New | 2022-08-08 | 62% |
| {Publiccloud} Use CloudCustodian as resource guardian | New | 2025-05-22 | 58% |
| Public Cloud Documentation | New | 2022-09-22 | 66% |
| {MinimalVM} MinimalVM Cloud image test automation | New | 2020-04-29 | 90% |
| {Publiccloud} Test Maintenance images | New | 2022-02-21 | 90% |
| {MinimalVM} separate hyperv from svirt backend | New | 2025-07-25 | 0% |
No active epics for this project
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 & Images | 137 | 89 | 29 |
Finished tickets this week