New, unlabelled issues requiring attention

Hi Triage Team,

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

In accordance with the issue triage workflow, we would like to ask you to:

1. Check for duplicates in this project and others (it is common for issues reported in EE to already exist in CE)
2. Add a type label
3. Add a team label
4. Add relevant subject labels
5. Mention relevant domain experts if the issue requires further attention

For the issues triaged please check off the box in front of the given issue.

• New Board scope milestone filter option
• "Could not connect to the CI server. Please check your settings and try again" error when it should not run in merge request using only: - tags@project
• Failed custom hook output not shown on Merge Request
• Auto DevOps container scanning job fails waiting for clair daemon to start
• Creating a project fails with error 500 - solved by fixing DNS resolution
• See all opened issues in the Open list within a board with scopes.
• Gitlab CI runners contact our webserver /downloads/packages.json
• Hide primary button and search filter on roadmap for unauthorized users
• Mails not sending to addresses behind corporate proxy
• documentation - autodevops json files structure
• Documentation: Unclarities about LDAP group sync
• "Something went wrong during merge pre-receive hook" on merge request due to the "Prevent committing secrets to Git" setting on upstream
• Kubernetes Ingress External IP address not displayed
• GitHub importer errors for renamed / redirected projects
• Dependency Scanning Errors on Multi-Module Maven Project

/cc @gitlab-org/issue-triage