Issues to apply severity and priority for Configure
Here is a list of issues without severity and priority:
-
Solve the explosion of cluster applications problem ~"Configure", ~"Monitoring" -
Credential rotation / dynamic secrets / secret variables ~"Configure", ~"Product Vision 2019", application control panel, ~"ci variables", ~"devops:configure", direction, ~"feature proposal" -
Configure multiple group-level clusters ~"Configure", ~"devops:configure", ~"kubernetes" -
AutoDevops doesn't create SSL/TLS secret and ingress controller logs errors ~"Configure", ~"auto devops", ~"bug", customer, ~"no-priority", ~"no-severity", reproduced on GitLab.com -
Update protected environments documentation to explicitly state that is under Feature Flag ~"Configure", ~"Documentation", ~"In review" -
Technical Discovery for Group-Level K8S Cluster Configuration ~"Configure", Deliverable, ~"kubernetes" -
Allow specifying protected environments through wildcards ~"Configure", ~"feature proposal" -
Add 'No one' option to Protected Environments dropdown ~"Configure", ~"feature proposal" -
Include 'Protected' bagde on Environments page if environment is protectd ~"Configure", ~"feature proposal" -
Add 'Last Deployment' column to Protected Environments ~"Configure", ~"feature proposal" -
Option for builds from protected environments to be picked up by protected runners ~"Configure", ~"feature proposal" -
API support for Protected Environments ~"Configure", ~"feature proposal" -
Kubernetes cluster optimization ~"Configure", GitLab Ultimate, ~"Monitoring", ~"Product Vision 2019", direction, ~"feature proposal", infrastructure monitoring, ~"kubernetes" -
Privilege escalation: Group clusters and ability to create projects ~"Configure", ~"devops:configure", ~"feature proposal", infrastructure configuration, security -
Extend GitLab ChatOps with Slack Custom Actions for Messages ~"Configure", auto updated, chatops, ~"devops:configure", ~"feature proposal", potential proposal
/cc @DylanGriffith