2020-08-31 - Triage report for "group::global search"
Hi, @JohnMcGuire @changzhengliu @mikelong
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-
#241807 Default to issue/MR search tab when user uses the syntax for IID Category:Global Search, devopsenablement, feature, groupglobal search, sectionenablement -
#239195 (closed) Add keyboard shortcut for search bar as /
Category:Global Search, devopsenablement, feature, featureaddition, groupglobal search, sectionenablement -
#239166 (closed) Search for issues/merge requests that you've recently looked at Category:Global Search, devopsenablement, feature, groupglobal search, sectionenablement -
#238532 (closed) Streamline searching for Merge requests by commit SHA Category:Global Search, devopsenablement, feature, groupglobal search, sectionenablement
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.
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 | 0 |
priority2 | 0 | 2 | 0 | 0 | 0 |
priority3 | 0 | 1 | 23 | 1 | 0 |
priority4 | 0 | 0 | 3 | 13 | 0 |
No priority | 0 | 0 | 4 | 2 | 16 |
customer
Unscheduled ~bug with-
#235134 (closed) Sidekiq continuously spawns elastic_commit_indexer jobs for 2 mirrored projects Category:Global Search, Enterprise Edition, ~"advanced global search", ~"bug", customer, devopsenablement, groupglobal search
Unscheduled ~bug (non-customer)
-
#240923 (closed) ElasticCommitIndexerWorker - ActiveRecord::InvalidForeignKey: PG::ForeignKeyViolation: ERROR: insert or update on table "index_statuses" violates foreign key ... Category:Global Search, ~"bug", devopsenablement, groupglobal search -
#238112 Search UI - Users can see private parent groups but not search them Category:Global Search, ~"bug", devopsenablement, groupglobal search, sectionenablement
Heatmap for ~missed-SLO bugs
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 | 0 |
priority2 | 0 | 2 | 0 | 0 | 0 |
priority3 | 0 | 0 | 0 | 0 | 0 |
priority4 | 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.yml.