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.
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.
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
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
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
QE-C Backlog Status
Latest Run: 2026-03-24 09:28:33 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
Bugs vs Features Backlog Length
This table compares the number of bugs against the planned tickets.
Incoming vs outcoming during the last 4 months
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
Public Cloud
Pickup time alerts
These tables show the tickets that are in violation of the SLO
Urgent Priority
High Priority
| Normal Priority: Public Cloud | 0 | 💚
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.
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.
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
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
New tickets
New tickets that are not workable and need clarification should be reviewed during the refinement meeting.
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
Epics
Container & Images Epics
Public Cloud Epics
No active epics for this project
Aging of tickets
Mesures the time since the ticket is created and the ticket is resolved
Aging tickets finished in the last 30 days
Other links
Finished tickets this week