2019-11-04 - Triage report for "group::application infrastructure security"

Hi, @stkerr @twoodham @leipert

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)

  • #35297 (closed) NetworkPolicy raw logs in GitLab UI Category:Container Network Security, ~"devops::defend", feature, ~"group::application infrastructure security"


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 04, 2019 by Sam Kerr
Assignee Loading
Time tracking Loading