Issues to apply severity and priority for CI/CD

Hi @erushton,

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.

• Review app dns generation creating non reachable apps ~"CI/CD", ~"bug", ~"devops:release"
• Overwriting/Deleting unintended secret variable via API calls ~"CI/CD", ~"bug", customer, customer+, pipeline
• Gitlab Kubernetes integration pod visualisation is incorrect, when multiple components are deployed ~"CI/CD", ~"bug", ~"devops:configure", ~"kubernetes"
• Name status checks consistently to support GitHub-integrated CI workflow ~"Accepting merge requests", ~"CI/CD", Deliverable, ~"S2", UX, ~"bug", customer, ~"devops:verify", direction, 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", ~"S4", backend, ~"bug", ~"devops:verify", ~"no-priority", ~"services"