2019-07-01 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:
- Check for duplicates in this project and others (it is common for issues reported in EE to already exist in CE).
- 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.
- Add a team label.
- Add a stage label.
- Add relevant subject labels to facilitate automatic addition of stage and group labels.
- 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!
-
#12502 (closed) Usage Ping - / +
-
#12499 (closed) post-migration to docker: 500 errors when editing or changing projects & group settings
@tnikic
-
#12497 (closed) 'Hide Whitespace Changes' checkbox has no effect, must refresh page to see result
-
#12494 (closed) backup / restore in gitlab-12.0.1-ee is intermittently failing to create valid single tar backup that can be restored
-
#12492 (closed) Merge request push rules error not notified in fast-forward mod
-
#12489 (closed) How to manually close the red X without starting auto devops?
-
#12485 (closed) Showing new vulnerabilities in Security Dashboard
-
#12483 (closed) Something went wrong while installing GitLab Runner
-
#12477 (closed) License management failing to parse python requirements file
-
#12471 (closed) Dependency Scanning Fails: "engine 'node' is incompatible with this module"
-
#12462 (closed) auto_link_ldap_user (and therefore login) fails if no email attribute is set on the LDAP object
-
#12454 (moved) Closing commits in merge request don't mark corresponding issues
-
#12441 (closed) Group board assignee scope stuck on single user, unable to set to "Any assignee"
Edited by Mark Fletcher