2019-08-16 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. 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! 🎉

@dchevalier2

• #13564 (closed) Custom metrics are still half-baked after a long time being GA

@jennielouie

• #13562 (closed) Viewing already merged Merge Requests fails with 500 after running BFG repo cleaner

@zeffmorgan

• #13551 (closed) Read-only acces token to the GitLab API

@markglenfletcher

• #13546 Enable whitelisting of groups for protected branches

@asoborov

• #13521 (closed) Burndown chart lines start at negative x-axis position and progress stops two days ago

@rymai

• #13516 CI: Add a link to "next run" and / or "latest run"