2019-10-14 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.
  1. Add a group label.
  2. Add a stage label.
  3. Add relevant category and facet 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! 🎉

@jennielouie

@niskhakova

@sliaquat

  • #33941 (closed) SAST should support git url substitution for golang builds
  • #33938 Have more fine grained actions on merge event webhooks

@dchevalier2

  • #33931 (closed) Unwanted navigation when searching in labels popover
  • #33928 Sort C/C++ Header Files before Source files in Merge Requests

@kwiebers

  • #33925 (closed) Merge train "previous ref does not exist" error
  • #33912 (closed) CI: "only: tags" is confused when the branch has the same name as another tag

@ddavison

  • #33903 (closed) Dashboard line-chart don't redraw correctly after enabling/disabling metrics
  • #33923 (closed) Gitlab server backup - duplicated backups

@tpazitny

  • #33898 (closed) Breadcrumbs way too short to be useful if you go 1-2 levels deep
  • #33893 (closed) API problem: Get url to specific file version/ content of file from specific commit

@rymai

  • #33889 (closed) Cross-promote GitLab Mattermost plugin
  • #33881 (closed) "Something went wrong on our end." when trying to disable jira comments on commits

@tmslvnkc

@grantyoung

Edited by Dan Davison