Feedback issue: Feedback on the automation of Bug Prioritization report
This issue is for providing feedback on the automation of Bug Prioritization report introduced in #1962
MR: gitlab-org/quality/triage-ops!2422 (merged)
The summary of changes include:
- Bug Prioritization report is created on the 2nd of every month for the
gitlab.org
and assigned to the PM's and EM's for each group
This report is generated with the Top 15-20 bugs in the respective product group*. The list of bugs is prioritised based on :
- Severity based on label
severity::*
andtype::bug
- Customer issues based on label
customer
- SLO Near Miss and SLO missed bugs
- Age of the issues(oldest)
- Security vulnerabilities based on label
bug::vulnerability
(Displayed in the last section)
Based on the feedback received for report, there was a second iteration of updates made for this report in gitlab-org/quality/triage-ops!2712 (merged)
List of Improvements made for this report based on the feedback:
- If a bug already has the current milestone assigned, then we can exclude it as its been looked upon
- Included SLOMissed and SLONear Miss labelled issues
- Displaying the Upvotes on the issues to determine the impact of fixing an issue
- There are few issues marked with workflowblocked labels, which we ignore from the report because it requires either a larger investment to resolve them, or they are dependent on another issue, potentially owned by another team
- Since bugvulnerability is mostly looked into immediately, add it as last section after showing the top level bugs
The recent list of reports can be viewed here
Any feedback is helpful, whether you liked the new process, disliked it, or felt indifferent, Please share!
Edited by Nivetha Prabakaran