Issues to apply severity and priority for CI/CD

Here is a list of issues without severity and priority:

• Gitlab Kubernetes integration pod visualisation is incorrect, when multiple components are deployed ~"CI/CD", ~"bug", ~"devops:configure", ~"kubernetes"
• Design bug: GitHub status checks should be named consistently, not per branch (or at least allow this option) ~"Accepting merge requests", ~"CI/CD", ~"bug", customer, ~"devops:verify", movingtogitlab
• Internal project uses build minutes ~"CI/CD", ~"bug", ~"devops:verify", pipeline, reproduced on GitLab.com
• Creating a new Pipeline errors: "The form contains the following error: Undefined error" ~"CI/CD", auto updated, awaiting feedback, ~"bug", pipeline
• Create CI/CD project from GitHub should match visibility of GitHub project ~"CI/CD", ~"bug", ~"devops:verify", ~"import", ~"no-priority", ~"no-severity"
• GitHub mirrored repos should be read-only ~"CI/CD", ~"bug", ~"devops:verify", ~"no-priority", ~"no-severity"
• Merge request pipelines link to wrong downstream Jenkins build. ~"CI/CD", ~"bug", ~"external services", pipeline
• CI/CD only GitHub project does not report pipeline status to Github until Test button is pressed in GitLab Integration page. ~"CI/CD", backend, ~"bug", ~"devops:verify", ~"no-priority", ~"no-severity", ~"services"

/cc @erushton