Geo group issues requiring attention
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.
- #11729 (closed) Geo: Provide better licensing information in Admin Panel ~"Geo", Geo Administration, UI component, feature
- #11257 (closed) Geo: Gracefully handle replication when there is a primary database node failover ~"Geo", Geo Administration, auto updated, customer, feature
- #11012 [Indie Computing] Open discussion for GitLab appliance for Geo use case ~"Geo", Geo Next Gen, auto updated, feature
- #10779 (closed) Geo: redirect /edit and /new routes to primary ~"Geo", UX, feature
- #9900 Selective Sync of Projects with restricted metadata ~"Geo", ~"Geo Replication/Sync", feature
- #9723 (closed) Geo: Database replication in the secondary cluster ~"Geo", ~"Geo Replication/Sync", customer+, database, feature
- #9410 (closed) Route /admin/geo gives 404 ~"Geo", Geo Administration, feature
- #9347 (closed) Geo: Handle rename/move/delete of Pages ~"Geo", ~"Geo Replication/Sync", feature
- #9341 (closed) Geo: Backfill GitLab Pages on secondaries ~"Geo", ~"Geo Replication/Sync", feature
- #9337 (closed) Geo: Replicate new GitLab Pages deploys on secondaries ~"Geo", ~"Geo DR", ~"Geo Replication/Sync", feature
- #9165 (closed) Improve usage pings about Geo ~"Geo", Geo Administration, auto updated, feature, ~"telemetry"
- #8168 (closed) Gitaly Replicas based on Geo replication Architecture decision, ~"Geo", ~"Geo DR", ~"Geo Replication/Sync", ~"Gitaly", feature
- #7919 (moved) Distributed build caching with GitLab Geo ~"Geo", ~"Geo Performance", direction, feature, ~"runner"
- #7845 (closed) Geo: Decide how we are going to expose Wiki synchronization information ~"Geo", UX, feature
- #7703 (closed) Better differentiate primary instance from secondaries visually in Admin Area ~"Geo", Geo Administration, UX, feature
Hi @rnienaber,
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.
- #11594 (closed) Geo: Redirect after authentication prevents access to secondary ~"Geo", Geo Administration, auto updated, ~"bug", customer, ~"workflow::In dev"
- #11173 (closed) Git push SSH proxy may not handle relative_url_root ~"Geo", Geo Administration, ~"bug", workflowready for development
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: