Geo group issues requiring attention
Heat map for bugs:
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 0 | 0 | 1 | 0 |
| ~P2 | 0 | 0 | 1 | 0 |
| ~P3 | 0 | 0 | 21 | 5 |
| ~P4 | 0 | 0 | 2 | 9 |
Hi @fzimmer,
Here is a list of feature proposals without a milestone.
We would like to ask you to determine whether this issue should be scheduled or closed. For each issue please:
- Close the issue out if it is no longer relevant or a duplicate.
- Assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
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.
-
#12646 (closed) Make gitlab-rake geo:status available on a Primary node ~"Geo", Geo Administration, devopsenablement, feature, groupgeo
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 Fabian Zimmer