2021-08-09 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:

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.

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

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

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

6. Add a stage label.

7. Add a group label.

8. Add relevant category labels to facilitate automatic addition of stage and group labels.

9. If needed, mention relevant domain experts if the issue requires further attention.

10. (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! 🎉

@at.ramya

• gitlab-org/gitlab#337425 (closed) Runner info in pipeline/job webhooks is sometimes empty
• gitlab-org/gitlab#337419 (closed) GitLab pages documentation has not been updated for source installations
• gitlab-org/gitlab#337410 Add difference for the description of SM and SaaS
• gitlab-org/gitlab#337409 Limiting jobs sharing a resource (making resource_group a counting semaphore ?) Category:Continuous Delivery, automation:ml, automation:ml wrong, ~"devops::release", ~"group::release", sectionops

@jo_shih

• gitlab-org/gitlab#337501 (closed) Docs feedback: CI/CD Caching: when the cache is cleared
• gitlab-org/gitlab#337495 (closed) Synced LDAP groups get cleared when LDAP user is locked ~"Category:Authentication and Authorization", automation:ml, devopsmanage, ~"group::access", sectiondev
• gitlab-org/gitlab#337499 Stopping environments through upstream automation:ml, devopsverify, grouppipeline authoring, sectionops
• gitlab-org/gitlab#337457 (closed) Provide docs on how to specify which executor is used to run a .gitlab-ci.yml

@kwiebers

• gitlab-org/gitlab#337451 (closed) Failure in browser_ui/3_create/merge_request/cherry_pick/cherry_pick_a_merge_spec.rb | Create Cherry picking from a merge request creates a merge request QA, Quality, failureinvestigating, ~"found:main", priority2, test
• gitlab-org/gitlab#337446 (closed) Pushing same Helm chart several times does not fail and add another artifact ~"Accepting merge requests", Category:Helm Chart Registry, devopspackage, ~"group::package", sectionops
• gitlab-org/gitlab#337441 Merge checks - Pipelines must succeed
• gitlab-org/gitlab#337429 Reset unauthenticated request rate limit for IP upon authentication

---

Job URL: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/1487086947