Configure group issues requiring attention
Hi @danielgruesso,
Here is a list of feature proposals without a milestone.
We would like to ask you to determine whether this issue should be scheduled or closed. For each issue please:
- Close the issue out if it is no longer relevant or a duplicate.
- Assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/9982 Allow user to install Hashicorp Vault into Kubernetes Cluster ~"Configure", Persona: DevOps Engineer, Persona: Development Team Lead, Persona: Systems Administrator, ~"devops:configure", feature, ~"kubernetes" -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9344 Allow a single environment to deploy to multiple Kubernetes clusters ~"Configure", UX, backend, customer, customer+, deploy, ~"devops:configure", feature, frontend, ~"kubernetes" -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9265 Netflix Ops for Everyone Else: NOFEE ~"Configure", ~"devops:configure", feature, infrastructure configuration -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9191 Disable third party offers by default for Premium and Ultimate customers ~"Configure", customer, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/8620 Ops interface to Istio ~"Configure", ~"devops:configure", feature, infrastructure configuration -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7807 Failure Injection Testing (FIT) or Chaos as part of operations features ~"Configure", GitLab Premium, ~"devops:configure", direction, feature, ~"moonshots" -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7181 Allow specifying protected environments through wildcards ~"Configure", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7174 Add 'No one' option to Protected Environments dropdown ~"Configure", feature, frontend -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7173 Include 'Protected' bagde on Environments page if environment is protectd ~"Configure", feature, frontend -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7172 Add 'Last Deployment' column to Protected Environments ~"Configure", feature, frontend -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7127 Option for builds from protected environments to be picked up by protected runners ~"Configure", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7068 API support for Protected Environments ~"Configure", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/6789 Be able to choose the pod, you wish to open a terminal to (Gitlab Kubernetes integration) ~"Configure", ~"devops:configure", feature, ~"kubernetes" -
https://gitlab.com/gitlab-org/gitlab-ee/issues/6736 (confidential) ~"(confidential)" -
https://gitlab.com/gitlab-org/gitlab-ee/issues/6154 Slack Custom Actions for Messages ~"Configure", auto updated, chatops, ~"devops:configure", feature, potential proposal
Hi @ClemMakesApps,
Here is a list of frontend bugs without severity and priority for the team.
We would like to ask you to work with your team to triage the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
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.
Hi @DylanGriffith,
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 the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
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.
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: