2020-07-06 - Triage report for "group::gitaly"
Hi, @jramsay @zj-gitlab @timzallmann
This is a group or stage level triage report that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
feature (non-customer)
Unscheduled-
#223105 Improve UI for storage weights Category:Gitaly, UX debt, auto updated, devopscreate, feature, groupgitaly -
#29653 automated gitaly storage nodes rebalancing Category:Gitaly, ~"P3", ~"S3", devopscreate, feature, groupgitaly, internal customer, production request
Unscheduled UX Debt Issues
-
#223105 Improve UI for storage weights Category:Gitaly, UX debt, auto updated, devopscreate, feature, groupgitaly
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.
~S1 | ~S2 | ~S3 | ~S4 | No severity | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 0 | 1 | 0 | 0 |
~P3 | 0 | 3 | 12 | 0 | 1 |
~P4 | 0 | 0 | 0 | 8 | 1 |
No priority | 0 | 1 | 4 | 2 | 7 |
Unscheduled ~bug (non-customer)
-
#224495 (closed) Git push failing for particular branch Category:Gitaly, ~"S3", ~"bug", devopscreate, groupgitaly -
#223839 (closed) Unable to push to branches - GIT_OBJECT_DIRECTORY and GIT_ALTERNATE_OBJECT_DIRECTORIES incorrectly set Category:Gitaly, ~"S2", ~"bug", devopscreate, groupgitaly -
#223200 (closed) GitLab + SubGit: Subversion commit appears in a git repository after 20minutes-1hour delay Category:Gitaly, Category:Source Code Management, ~"S4", ~"bug", devopscreate, groupgitaly -
#20103 (closed) Make dashboard and project page resilient to missing filesystem or Gitaly access Category:Gitaly, Quality, ~"availability", ~"bug", devopscreate, groupgitaly, repository
Heatmap for ~missed-SLO bugs
~S1 | ~S2 | ~S3 | ~S4 | No severity | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 0 | 1 | 0 | 0 |
~P3 | 0 | 0 | 0 | 0 | 0 |
~P4 | 0 | 0 | 0 | 0 | 0 |
No priority | 0 | 0 | 0 | 0 | 0 |
This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
If assignees or people mentioned in this individual triage report need to be amended, please edit group_definition.rb.