Issues to apply severity and priority for Manage

Hi @lmcandrew,

Here is a list of bugs without severity and priority for the team.

We would like to ask you to:

Work with your team to triage and add a severity label (~S1 / ~S2 / ~S3 / ~S4) and a priority label (~P1 / ~P2 / ~P3 / ~P4) to the issues in this list.

The definition of these labels are defined at:

• Priority Labels
• Severity Labels

For the issues triaged please check off the box in front of the given issue.

Please work with your team to complete the list this week.

• TODOs about epics do not link to at-mentioned users ~"Manage", ~"bug", epics
• Cannot set explicit group permission that matches inherited permission ~"Manage", ~"bug", reproduced on GitLab.com, subgroups
• Empty required_groups results in blocked users getting unblocked. ~"Manage", ~"bug", ~"devops:manage", saml, ~"user management"
• LDAP sync job doesn't add new SSH keys if at least one key already exists ~"Manage", ~"bug", ~"devops:manage", ldap, ~"user management"
• Milestones from Archived Project are Displayed at Group Level ~"Manage", ~"bug", milestones, project
• LDAP Group Sync by Filter doesn't sanitize DNs ~"Manage", ~"bug", customer, ldap
• Docs feedback: Custom project template doc not up to date ~"Documentation", ~"Manage", admin dashboard, awaiting feedback, ~"bug", ~"devops:manage", ~"project templates"
• Creating a project fails with error 500 - solved by fixing DNS resolution ~"Manage", ~"audit events", ~"bug", ~"devops:manage", needs investigation
• Group Member Lock is accessible to group members with maintainer role ~"Manage", ~"bug", customer, ~"groups", permissions
• Updating user email doesn't work when user synced attributes exist ~"Manage", ~"bug", customer, ldap, ~"no-priority", ~"no-severity"