Skip to content

Use `-` instead of `0` in issue heatmaps when no issues are found

What does this MR do and why?

What: Use - instead of 0 in issue heatmaps when no issues are found.

Why: This makes issue heatmaps easier and faster to read when they are mostly empty (e.g. security section).

Contributes to #1466.

Screenshots

Expected results in a team triage report:

Before After
Screenshot_2024-02-19_at_14.24.27 Screenshot_2024-02-19_at_14.25.55

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.

Example https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/6535781428

Click to expand

Hi @andr3 @andyvolpe @francoisrose @phikai,

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

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.
  • 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.

Feature Proposal Section

For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.

Unscheduled ~feature with customer


Unscheduled ~feature (non-customer)


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.

  • Engineering Managers: Please add a severity label for those issues without one
  • Product Designers: Please add a severity label to UX ~bug issues without one

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.

severity1 severity2 severity3 severity4 No severity
priority1 - - 1 - -
priority2 3 6 13 - 1
priority3 - 1 55 11 -
priority4 - - 12 55 -
No priority - 1 37 29 55

Heatmap for customer bugs

severity1 severity2 severity3 severity4 No severity
priority1 - - - - -
priority2 - - 5 - -
priority3 - - 28 3 -
priority4 - - 6 18 -
No priority - 1 16 7 5

Unscheduled frontend ~bug with customer


Unscheduled frontend ~bug (non-customer)


Unscheduled ~bug with customer


Unscheduled ~bug (non-customer)


Heatmap for SLOMissed bugs

severity1 severity2 severity3 severity4 No severity
priority1 - - - - -
priority2 1 5 11 - -
priority3 - 1 43 9 -
priority4 - - 9 42 -
No priority - - 27 20 -

Heatmap for SLOMissed bugs (stuck issues)

severity1 severity2 severity3 severity4 No severity
No assignees - 4 88 67 -
No milestone 1 3 33 21 -
Milestone: Backlog - 2 55 48 -
Milestone in the past - - - - -

Heatmap for vintage bugs

severity1 severity2 severity3 severity4 No severity
priority1 - - - - -
priority2 - 1 7 - -
priority3 - - 30 9 -
priority4 - - 10 30 -
No priority - - 13 14 7

Heatmap for blocked bugs

severity1 severity2 severity3 severity4 No severity
priority1 - - - - -
priority2 - 1 2 - -
priority3 - - - - -
priority4 - - - - -
No priority - - - - -

New untriaged community issues (last 7 days with no ~type label)


Action items

Edited by Peter Leitzen

Merge request reports