Configure group issues requiring attention
Heat map for bugs:
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 0 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 1 | 1 | 0 |
| ~P4 | 0 | 0 | 0 | 1 | 0 |
| ~"No priority" | 0 | 0 | 0 | 1 | 1 |
Hi @DylanGriffith,
Here is a list of bugs without severity and priority for the team.
We would like to ask you to work with your team to triage the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
-
#12852 (closed) Infinite spinner in deployment board ~"Configure", ~"bug", ~"devops::configure", ~"group::autodevops and kubernetes", regression, regression:12.1 -
#12781 (closed) DNS label is too long for Auto Deploy to Staging, causing TLS failure ~"Configure", ~"S4", ~"bug", ~"devops::configure", ~"group::autodevops and kubernetes"
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
Edited by Dylan Griffith (ex GitLab)