2019-12-05 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! 🎉

@rymai

@wlsf82

  • #38218 (closed) start_in is limited to 1 day when it is advertised to only be limited to 1 week

@zeffmorgan

  • #38217 Isolate multiple merge request pipeline results

@markglenfletcher

  • #38216 (closed) Cannot access private repo merge request source (API or clone)

@kwiebers

  • #38215 No way to pick just the project name for badges

@dchevalier2

  • #38138 (closed) YAML anchors for script should work with include from another yml file

@asoborov

@ddavison

  • #38117 Ability to ignore work in progress merge requests for mattermost notifications

@tmslvnkc

@jennielouie

  • #38099 Assign issues to closed milestones

@sliaquat

@godfat

@caalberts

@mlapierre

  • #38074 (closed) only:changes in combination with recommended merge_request produces unexpected runs

@tpazitny

  • #38072 (closed) Group milestones are not showing the issues that are assigned to them

@grantyoung

@at.ramya

  • #38030 (closed) [Protected branch allowed to merge] Maintainer can merge even if set to "No one"

@niskhakova

Edited by Dan Davison