2021-11-18 Untriaged issues requiring initial triage
Hi Triage Team,
Here is a list of the issues that do not meet the triaged criteria in accordance with the Partial triage guidelines, we would like to ask you to:
-
If the issue is spam, report the abuse and make the issue confidential. Flag the report that is raised in the
#abuse
Slack channel with a link to the issue and alert the@abuse-team
. -
If the issue is a request for help, you can use this template to provide resources and close the issue:
Hey @author. Based on the information given, this request for support is out of the scope of the issue tracker (which is for new bug reports and feature proposals). Unfortunately, I won't be able to help get it resolved. However, for support requests we have several resources that you can use to find help and support from the Community, including: * [Technical Support for Paid Tiers](https://about.gitlab.com/support/) * [Community Forum](https://forum.gitlab.com/) * [Reference Documents and Videos](https://about.gitlab.com/get-help/#references) Please refer to our [Support page](https://about.gitlab.com/support/) for more information. If you believe this was closed in error, please feel free to re-open the issue. /label ~"support request" /close
- If the issue is re-opened after you closed it, you should get an email notification and would then be responsible for re-evaluating the issue.
- (Optional) Alternatively, instead of closing the issue when using the template above, you could take on the role of customer support and ask the reporter for more information so we can properly assist them. If you do this, add the awaiting feedback label.
-
Check for duplicate issues. If identified as a duplicate, the new issue can be closed with a note similar to:
Hey @author. Thanks for creating this issue, but it looks like a duplicate of #issue. I'm closing this issue in favour of #issue. Please add your thoughts and feedback on #issue (don't forget to upvote feature proposals). /duplicate #issue
- Do not make any forward looking statements around milestone targets that the duplicate issue may be assigned.
-
If it is unclear whether the issue is a bug or a support request:
-
@mention
the PM/EM for the relevant group and ask for their opinion.
-
-
Add a type label.
- If identified as a bug, add a severity label.
- If the severity is severity1 or severity2, mention relevant PM/EMs from the relevant stage group from product devstages categories.
-
Add a stage label.
-
Add a group label.
-
Add relevant category labels to facilitate automatic addition of stage and group labels.
-
If needed, mention relevant domain experts if the issue requires further attention.
-
(Optional) Mention relevant PM/EMs from the relevant stage group from product devstages categories.
For the issues triaged please check off the box in front of the given issue.
Once you've triaged all the issues assigned to you, you can unassign and unsubscribe yourself via these quick actions:
/done
/unassign me
/unsubscribe
When all the checkboxes are done, close the issue, and celebrate!
-
gitlab-org/gitlab#345471 Allow sorting runners by description -
gitlab-org/gitlab#345456 (closed) Add the feature described in issue 36118 to GitLab's Community Edition -
gitlab-org/gitlab#345449 (closed) Field value is visible in Dark Mode of Mirror user input field Category:Source Code Management, automation:ml, devopscreate, groupsource code, sectiondev -
gitlab-org/gitlab#345447 (closed) UX is improved for Git repository URL input of mirroring repositories feature Category:Source Code Management, automation:ml, devopscreate, groupsource code, sectiondev
-
gitlab-org/gitlab#345437 (closed) Human readable error instead of 500 error page is shown for mirroring repositories feature used with specific input Category:Source Code Management, automation:ml, devopscreate, groupsource code, sectiondev -
gitlab-org/gitlab#345427 Automatic runner token rotation -
gitlab-org/gitlab#345414 New user, pushing any branch results in failed pipeline with 0 jobs -
gitlab-org/gitlab#345413 (closed) Failure in api/1_manage/bulk_import_project_spec.rb | Manage Bulk project import with project issues successfully imports issue QA, Quality, failureinvestigating, ~"found:main", priority2, test
-
gitlab-org/gitlab#345408 (confidential) ~"(confidential)" -
gitlab-org/gitlab#345402 node16 issue using gitlab runner -
gitlab-org/gitlab#345397 Configure MR pipeline notifications customer -
gitlab-org/gitlab#345387 (closed) Failure in api/3_create/gitaly/backend_node_recovery_spec.rb | Create Gitaly Backend node recovery recovers from dataloss QA, Quality, failureinvestigating, ~"found:main", priority2, test
-
gitlab-org/gitlab#345507 (closed) Failure in browser_ui/4_verify/pipelines_for_merged_results_and_merge_trains_spec.rb | Verify Pipelines for merged results and merge trains merges via a merge train Enterprise Edition, QA, Quality, failureinvestigating, ~"found:main", priority2, test -
gitlab-org/gitlab#345500 fetch count not working from the project statistics API -
gitlab-org/gitlab#345477 (closed) Resolve multi-path alias for webpack -
gitlab-org/gitlab#345476 typo in Russian translate
Job URL: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/1794575011