2019-06-28 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 Level 1 triage guidelines, 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.

• If identified as a bug, add a severity label.
• If the severity is ~S1 or ~S2, mention relevant PM/EMs from the relevant stage group from product devstages categories.

1. Add a team label.
2. Add a stage label.
3. If possible, add relevant subject labels.
4. If needed, 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.

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! 🎉

@asoborov

• #12471 (closed) Dependency Scanning Fails: "engine 'node' is incompatible with this module"

@wlsf82

• #12469 (closed) Can't assign group milestone to project issue board

@rymai

• #12465 (closed) elasticsearch indexing fails when no master in project

@dchevalier2

• #12462 (closed) auto_link_ldap_user (and therefore login) fails if no email attribute is set on the LDAP object

@markglenfletcher

• #12458 (closed) Upgrade 11.11.4 to 12.0.2 caused noticeable downtime (despite zero downtime procedure being used)

@tnikic

• #12454 (moved) Closing commits in merge request don't mark corresponding issues

@godfat

• #12441 (closed) Group board assignee scope stuck on single user, unable to set to "Any assignee"