Skip to content

Adding details for Bug Prioritization triage report in handbook page

Nivetha Prabakaran requested to merge nprabakaran-master-patch-b3ba into master

Why is this change being made?

A new Bug Prioritization report is created by the traige-ops and this report will be used for the Bug Prioritization process by the product groups.

The report is generated with issues that are prioritized based on the below conditions:

  1. Severity based on label severity::* and type::bug
  2. Security vulnerabilities based on label bug::vulnerability
  3. Customer issues based on label customer
  4. Age of the issues(oldest)

The existing process of SETs using the bug prioritization dashboard will be deprecated by this change as the process is automated. Still the products groups can prefer to use the bug prioritization dashboard, so the relevant information is updated

Related issue: gitlab-org/quality/quality-engineering/team-tasks#1962 OKR: https://gitlab.com/gitlab-com/gitlab-OKRs/-/work_items/3904

Triage-ops MR - gitlab-org/quality/triage-ops!2422 (merged)

Sample report - https://gitlab.com/gitlab-org/quality/triage-reports/-/issues/14732 and https://gitlab.com/gitlab-org/quality/triage-reports/-/issues/14733

CHANGEME - add the details saying why, not just what.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Nivetha Prabakaran

Merge request reports