2019-11-04 - Triage report for "group::system"

Hi, @nagyv.gitlab @nicholasklick @jeanduplessis

This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:

  • https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-packages

Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:

  • Determine if the issue should be closed if it is no longer relevant or a duplicate.
  • If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
  • Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
    • https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels
  • Once a milestone has been assigned please check off the box for that issue.
  • Please work with your team to complete the list by the due date set.

Unscheduled feature (non-customer)

  • #34215 (closed) JAMStack Project template ~"devops::configure", feature, ~"group::system", workflowproblem validation
  • #34026 (closed) GitLab managed Serverless provider ~"devops::configure", feature, ~"group::system", workflowproblem validation
  • #33807 (closed) Check out how can we use GitLab Prometheus with CloudWatch ~"devops::configure", feature, ~"group::system", workflowproblem validation
  • #33805 (closed) Project template for JavaScript serverless project UX, ~"devops::configure", direction, documentation, feature, ~"group::system", workflowready for development
  • #33794 (closed) Scheduled serverless events ~"devops::configure", feature, ~"group::system", workflowvalidation backlog
  • #33653 (closed) Backup config for GitLab Managed Clusters Category:Infrastructure as Code, Dogfooding, ~"devops::configure", feature, ~"group::system", workflowvalidation backlog
  • #33559 (closed) Configure mTLS certs when someone uses a serverless domain ~"devops::configure", feature, ~"group::system", workflowready for development
  • #32686 (closed) Allow central log-collection of Knative function logs Category:Serverless, ~"devops::configure", feature, ~"group::system", workflowsolution validation
  • #32383 (closed) Automate Access Requests with Gitlab Serverless functions Category:Serverless, ~"devops::configure", feature, ~"group::system", workflowproblem validation
  • #30766 (closed) Make it possible to update Knative Category:Serverless, ~"devops::configure", feature, ~"group::system", workflowsolution validation
  • #30752 (closed) Automatically test lambda functions Category:Serverless, ~"Serverless [DEPRECATED]", ~"devops::configure", direction, feature, ~"group::system", workflowsolution validation
  • #30547 (closed) Integrate GitLab with lambda serverless application template creation Alliances, Alliances - AWS, Category:Serverless, ~"devops::configure", feature, ~"group::system", workflowproblem validation
  • #29093 (closed) Serverless GitLab Events ~"Accepting merge requests", Category:Serverless, UX, backend, ~"devops::configure", feature, frontend, ~"group::system", workflowvalidation backlog
  • #28488 (closed) Kubernetes > Knative > Display domain/endpoint for istio-ingress installs Category:Serverless, ~"Serverless [DEPRECATED]", ~"UX ready", backend, ~"devops::configure", feature, ~"group::system"
  • #28386 (closed) Add cron job specification to a serverless function Category:Serverless, ~"Serverless [DEPRECATED]", ~"devops::configure", feature, ~"group::system"

Bug Section

For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.

Heatmap for all bugs

Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.

~S1 ~S2 ~S3 ~S4 ~"No severity"
~P1 0 0 0 0 0
~P2 0 0 1 0 0
~P3 0 0 0 0 0
~P4 0 0 0 3 1
~"No priority" 0 0 0 0 3

Unscheduled ~bug (non-customer)

  • #34644 (closed) Incorrect Knative version stored in the database after creating a Cloud Run on GKE cluster Category:Serverless, ~"P2", ~"S3", ~"bug", ~"devops::configure", ~"group::system"
  • #34372 (closed) Serverless function description missing on Knative 0.7 Category:Serverless, ~"bug", ~"devops::configure", ~"group::system", ~"workflow::In review"


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:

  • https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-packages
Edited Nov 07, 2019 by Nick Klick
Assignee Loading
Time tracking Loading