New, unlabelled issues requiring attention

Hi Triage Team,

Here is a list of the latest issues without labels in the project.

In accordance with the issue triage workflow, 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
  3. Add a team label
  4. Add relevant subject labels
  5. 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.

  • Add weight as possible board list for estimation meetings
  • Global search return wrong result
  • Option to disable offers of EE features on a functionally CE instance
  • Cannot revert to default labels for group board
  • GitLab UI not reporting stderr with pre-receive custom_hooks
  • CI/CD Artifact upload fails
  • Special licence pricing for startups and/or low-income countries
  • Automatically expand collapsed file if clicked from the tree view
  • LDAP sync job doesn't add new SSH keys if at least one key already exists
  • Cannot create issue on board for projects within subgroups.
  • Add project in Operations fails with useless error message
  • Add option to allow branch mirroring to bypass protected branch & push rules
  • Milestones from Archived Project are Displayed at Group Level
  • FindSecBugs not accepting a custom Maven settings.xml file
  • pdf.js bundled GitLab cannot render CJK characters
  • Pipeline test output in mergerequest too narrow
  • Code climate report in MR
  • Squashing MR doesn't use the latest (updated) MR's title
  • Variable Substitution on multiple includes
  • Usage of variables in only: changes: paths
  • "Could not connect to the CI server. Please check your settings and try again" error when it should not run in merge request using only: - tags@project
  • Failed custom hook output not shown on Merge Request

/cc @gitlab-org/triage

Edited Nov 15, 2018 by Mark Fletcher
Assignee Loading
Time tracking Loading