Issues to apply severity and priority for Create

Here is a list of issues without severity and priority:

• When 'self-approval' is enabled no 'explicit approvers' (or not enough users) are set - allow authors to self-approve ~"Create", approvals, backend, ~"bug", customer, ~"no-priority", ~"no-severity"
• Mirror authentication has no "username" field ~"Create", ~"bug", customer, ~"devops:create", ~"mirror", ~"no-priority", ~"no-severity"
• Approving a MR then editing a file doesn't reset the approvals ~"Create", approvals, awaiting feedback, ~"bug", customer, ~"devops:create", merge requests
• Mirror pull API endpoint returns 404 ~"Create", api, auto updated, ~"bug", customer, ~"devops:create", ~"mirror", ~"no-priority", ~"no-severity", regression
• New branch push is incorrectly failing size file gitlab hook ~"Create", ~"bug", ~"devops:create", needs investigation, repository
• Any eligible user can approve merge request with full approval count ~"Create", Stretch, approvals, backend, ~"bug", merge requests, ~"no-priority", ~"no-severity"
• Race condition regarding MWPS and Approvals ~"Create", approvals, ~"bug", merge requests, ~"no-priority", ~"no-severity"
• Keep approvals when rebasing through the UI with reset approvals on push enabled ~"Create", approvals, auto updated, ~"bug", customer, ~"feature proposal", merge requests, ~"no-priority", ~"no-severity", regression
• Microsoft Teams integration shows incorrect message for 'approved' Merge Request event ~"Create", approvals, backend, ~"bug", merge requests, ~"services"
• Approval list is empty and cannot be merged ~"Create", approvals, ~"bug", ~"devops:create", merge requests, subgroups

/cc @DouweM