2019-07-25 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. Add relevant subject labels to facilitate automatic addition of stage and group 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

• #13031 Own wildcard TLS for Auto DevOps to Kubernetes deployments

@rymai

• #13028 (confidential) ~"(confidential)"

@sliaquat

• #13024 (closed) ActiveDirectory Group Inheritance moving intermediate group cause losing access

@jennielouie

• #13021 (moved) Issues not closed when MR targets not the default branch

@grantyoung

• #13012 Visual Review posts incorrect browser url (can expose access-token)

@mlapierre

• #13000 (closed) Triggers are not executed on retry if pipeline fails on first run

@tnikic

• #12995 (moved) Typo in new user tour