2020-09-10 Newly created unlabelled issues requiring initial triage

Hi Triage Team,

Here is a list of the latest issues without labels in the project.

In accordance with the Partial triage guidelines, we would like to ask you to:

1. 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.

2. 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.

1. 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

2. 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.

1. 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.

1. Add a stage label.
2. Add a group label.
3. Add relevant category and facet labels to facilitate automatic addition of stage and group labels.
4. If needed, mention relevant domain experts if the issue requires further attention.
5. (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 yourself with the /unassign me quick action.

When all the checkboxes are done, close the issue, and celebrate!

@at.ramya

• gitlab-org/gitlab#247115 (closed) "Setting the environment scope" is not labeled as being PREMIUM only

@caalberts

• gitlab-org/gitlab#246817 Provide GitLab PyPI Repository predefined environment variable

@chloeliu

• gitlab-org/gitlab#247465 (closed) Typo in class name of submit button on merge requests settings form

@dchevalier2

• gitlab-org/gitlab#247129 (closed) When I run bundle update, the compiler has run for a long time until os OOM killed ruby process

@ddavison

• gitlab-org/gitlab#246501 asciidoc: better rendering of table of content (ToC)

@ebanks

• gitlab-org/gitlab#247376 (closed) Flaky test: /spec/features/merge_request/batch_comments_spec.rb:187

@godfat-gitlab

• gitlab-org/gitlab#247138 (closed) conan install fails even if there is a valid community package

@grantyoung

• gitlab-org/gitlab#247074 (closed) "Checking pipeline status" for a merge request should include the reason why the check is still in progress

@jennielouie

• gitlab-org/gitlab#246784 (closed) CI Pipelines fail for API commits using Project Access Token

@jo_shih

• gitlab-org/gitlab#245191 (closed) ActionView::Template::Error with 4:Deadline Exceeded

@kwiebers

• gitlab-org/gitlab#247137 (closed) [Feature flag] Rollout of ci_send_deployment_hook_when_start

@markglenfletcher

• gitlab-org/gitlab#247090 Missing users on auto-completion for private projects shared with multiple groups

@mlapierre

• gitlab-org/gitlab#247450 (confidential) ~"(confidential)"

@niskhakova

• gitlab-org/gitlab#247104 (closed) Move README.md above File List in Project overview

@nwestbury

• gitlab-org/gitlab#247374 (closed) Plugin works locally, but not on gitlab pipeline (plugins not loaded)

@rymai

• gitlab-org/gitlab#247468 (confidential) ~"(confidential)"

@sliaquat

• gitlab-org/gitlab#247466 (closed) Default Code Quality Job is failing on lib/gitlab/ci/templates/utils/env.sh

@svistas

• gitlab-org/gitlab#247089 (closed) Why use LetsEncrypt

@tomi

• gitlab-org/gitlab#247461 (closed) Setting up two factor authentication (2FA) always yields invalid pin for some users

@tpazitny

• gitlab-org/gitlab#247459 (closed) Atom feed 500 error after SVN project migration

@treagitlab

• gitlab-org/gitlab#247474 (closed) Not able to close the Merge Request

@vincywilson

• gitlab-org/gitlab#247075 (closed) Kubernetes cluster service token now mandatory?

@willmeek

• gitlab-org/gitlab#246993 (closed) how can I use the Network storage to stored some codes

@zeffmorgan

• gitlab-org/gitlab#246757 (confidential) ~"(confidential)"