2020-08-31 - Triage report for "Quality"
Hi, @at.ramya @jo_shih @tpazitny @vincywilson @kwiebers
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.
Quality + QA unscheduled issues
-
gitlab-org/gitlab#242062 (closed) db:migrate fails | 998_gitlab_instance_administration_project QA, Quality, devopsmonitor, failuretest-environment, found:master, ~"group::apm", priority1, sectionops, test, workflowverification -
gitlab-org/gitlab#241762 (closed) Failure in qa/specs/features/api/3_create/repository/files_spec.rb:15 | Status code 400 QA, Quality, devopscreate, failureinvestigating, found:staging.gitlab.com, sectiondev, test -
gitlab-org/gitlab#241753 (closed) Failure in qa/specs/features/ee/browser_ui/3_create/merge_request/add_batch_comments_in_merge_request_spec.rb:41 | diff review QA, Quality, devopscreate, failureinvestigating, found:staging.gitlab.com, sectiondev, test -
gitlab-org/gitlab#241622 (closed) Failure in qa/specs/features/ee/browser_ui/2_plan/epic/roadmap_spec.rb:22 | Capybara::ElementNotFound QA, Quality, devopsplan, failuretest-environment, found:canary.gitlab.com, sectiondev, test -
gitlab-org/gitlab#241546 (closed) Failure in qa/specs/features/ee/browser_ui/8_monitor/cluster_with_prometheus | after(:context) @cluster.remove! QA, Quality, devopsmonitor, failureinvestigating, found:master, found:staging-orchestrated, sectionops, test -
gitlab-org/gitlab#241316 (closed) Failure in qa/specs/features/browser_ui/8_monitor/all_monitor_core_features_spec.rb:19 | WaitExceededError QA, Quality, devopsmonitor, failuretest-environment, found:staging-orchestrated, sectionops, test -
gitlab-org/gitlab#241315 (closed) Failure in qa/specs/features/browser_ui/8_monitor/all_monitor_core_features_spec.rb:13 | Ambiguous match QA, Quality, devopsmonitor, found:staging-orchestrated, sectionops, test -
gitlab-org/gitlab#241313 (closed) Failure in qa/specs/features/ee/browser_ui/secure/project_security_dashboard_spec.rb | QA, Quality, devopssecure, failureinvestigating, found:staging.gitlab.com, ~"section::securedefend", test -
gitlab-org/gitlab#241312 (closed) Failure in qa/specs/features/ee/browser_ui/3_create/repository/pull_mirroring_over_http_spec.rb | update source_project_uri QA, Quality, devopscreate, failureinvestigating, found:staging.gitlab.com, sectiondev, test -
gitlab-org/gitlab#241062 (closed) Failure in api/3_create/repository/files_spec.rb:96 | no-cache headers not as expected QA, Quality, devopscreate, failureinvestigating, found:staging.gitlab.com, sectiondev, test -
gitlab-org/gitlab#241021 (closed) Failure in review_merge_request_spec:23 | ide.commit_changes WaitExceededError QA, Quality, devopscreate, found:master, needs investigation, sectiondev -
gitlab-org/gitlab#240984 (closed) Failure in all_monitor_core_features_spec.rb:81 | QA::Git::Repository::RepositoryCommandError: QA, Quality, devopsmonitor, found:master, found:staging-orchestrated, needs investigation, sectionops, test -
gitlab-org/gitlab#239320 (closed) ee/browser_ui/3_create/repository/file_locking_spec.rb:80 # Create File Locking locks a file and unlocks in list QA, Quality, devopscreate, failureflaky-test, found:staging-orchestrated, sectiondev, test -
gitlab-org/gitlab#239319 (closed) browser_ui/8_monitor/all_monitor_core_features_spec.rb:32 # Monitor with Prometheus in a Gitlab-managed cluster duplicates to create dashboard to custom QA, Quality, devopsmonitor, failureflaky-test, found:staging-orchestrated, sectionops, test -
gitlab-org/gitlab#239300 (closed) Failure in /qa/specs/features/ee/browser_ui/2_plan/issue_boards/configure_issue_board_by_label_spec.rb:26 # Plan Configure issue board by label shows only issues that match the configured label QA, Quality, found:master -
gitlab-org/gitlab#239091 (closed) qa/specs/features/browser_ui/3_create/snippet/clone_push_pull_project_snippet_spec.rb:39 | Create Version control for project snippets clones, pushes, and pulls a project snippet over HTTP, edits via UI ~"Category:Snippets", QA, Quality, devopscreate, failureinvestigating, found:staging.gitlab.com, groupsource code, sectiondev, test -
gitlab-org/gitlab#238170 (closed) Failure in qa/specs/features/ee/browser_ui/secure/license_compliance_spec.rb | expected to find css "[data-qa-selector={{title}}quot;pipeline_commit_status{{title}}quot;],.qa-pipeline-commit-status" at least 1 time but there were no matches QA, Quality, devopssecure, failuretest-environment, found:staging.gitlab.com, groupcomposition analysis, test -
gitlab-org/gitlab#220752 (closed) Failure in qa/specs/features/ee/browser_ui/1_manage/instance/instance_audit_logs_spec.rb - 500 Error QA, Quality, devopsmanage, failureinvestigating, found:staging.gitlab.com, missed:13.1, missed:13.2, missed:13.3, priority1, sectiondev, test -
gitlab-org/gitlab#216622 (closed) Transient failure in qa/specs/features/browser_ui/1_manage/login/log_into_mattermost_via_gitlab_spec.rb QA, Quality, devopsmanage, failureinvestigating, found:master, sectiondev, test
Heatmap for triage failures
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 1 | 2 | 0 | 35 |
| priority2 | 0 | 0 | 1 | 0 | 8 |
| priority3 | 0 | 0 | 0 | 0 | 4 |
| priority4 | 0 | 0 | 0 | 0 | 6 |
| No priority | 0 | 0 | 0 | 0 | 107 |
Heatmap for all triage failures past SLO
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 0 | 1 | 0 | 0 |
| priority2 | 0 | 0 | 0 | 0 | 1 |
| priority3 | 0 | 0 | 0 | 0 | 0 |
| priority4 | 0 | 0 | 0 | 0 | 1 |
| No priority | 0 | 0 | 0 | 0 | 1 |
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.
Edited by Tanya Pazitny