2019-08-26 - Triage report for "group::telemetry"

Hi, @tipyn @jameslopez

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 gitlab-ce~2278648, 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://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md#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)

  • gitlab-ce#56320 Include previous errors in usage ping gitlab-ce8340534, gitlab-ce10697854, gitlab-ce10230929, gitlab-ce3338745
  • gitlab-ce#55872 Group/Project usage ping gitlab-ce8340534, gitlab-ce7161201, gitlab-ce10697854, gitlab-ce10230929, gitlab-ce~3338745
  • gitlab-ce#46437 Add fork network metrics to usage ping gitlab-ce7156613, gitlab-ce2278658, gitlab-ce3103452, gitlab-ce10230929, gitlab-ce3338745, gitlab-ce3081817
  • gitlab-ce#45853 Add data from /admin/dashboard/stats to usage ping gitlab-ce7161201, gitlab-ce2677574, gitlab-ce2677575, gitlab-ce24926493, gitlab-ce4116705, gitlab-ce10230929, gitlab-ce~3338745
  • gitlab-ce#33079 Exponential backoff for sending usage ping gitlab-ce2278656, gitlab-ce2677574, gitlab-ce2677575, gitlab-ce10230929, gitlab-ce~3338745
  • gitlab-ce#30442 Add number of users per access level in the usage ping gitlab-ce7156613, gitlab-ce7161201, gitlab-ce24926493, gitlab-ce10697854, gitlab-ce10230929, gitlab-ce3338745
  • gitlab-ce#51109 Include runners in usage ping "Category::Runner", gitlab-ce8338241, gitlab-ce3103453, gitlab-ce10230929, gitlab-ce~3338745

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.

gitlab-ce~3713903 gitlab-ce~3713902 gitlab-ce~3713901 gitlab-ce~3713900
gitlab-ce~3857370 0 0 0 0
gitlab-ce~3857523 0 0 0 0
gitlab-ce~3857529a 0 0 1 0
gitlab-ce~3857543 0 0 0 0

Unscheduled ~bug with customer

  • gitlab-ce#37819 ConvDevIndex: Data is still calculating... gitlab-ce3857529a, gitlab-ce3713901, gitlab-ce2278648, gitlab-ce3412207, gitlab-ce1672341, gitlab-ce10697854, gitlab-ce~3338745


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
Assignee Loading
Time tracking Loading