97
edits
BugBot: Difference between revisions
→Active Rules: Add a section about the inactive telemetry alerts rule.
(Tag removed tools) |
(→Active Rules: Add a section about the inactive telemetry alerts rule.) |
||
| (16 intermediate revisions by 5 users not shown) | |||
| Line 14: | Line 14: | ||
= Active Rules = | = Active Rules = | ||
{{BugBotRule | {{BugBotRule | ||
| Rule ID = 163 | |||
| Rule name = Variant Expiration | | Rule name = Variant Expiration | ||
| Purpose = Follow up on variants that need to be dropped or extended | | Purpose = Follow up on variants that need to be dropped or extended | ||
| Line 24: | Line 25: | ||
| Action = Close the bug as "INVALID" and move it to the "Invalid Bugs" product | | Action = Close the bug as "INVALID" and move it to the "Invalid Bugs" product | ||
| Source = spambug.py | | Source = spambug.py | ||
}} | |||
{{BugBotRule | |||
| Rule name = File bugs for new actionable crashes | |||
| Purpose = Automate discovering actionable crash reports to speed up fixes, reduce user impact, and save engineering time. | |||
| Action = Open a crash bug with the relevant information | |||
| Source = file_crash_bug.py | |||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Line 54: | Line 61: | ||
| Action = Set the 'Has STR' field to be 'yes' | | Action = Set the 'Has STR' field to be 'yes' | ||
| Source = has_str_no_hasstr.py | | Source = has_str_no_hasstr.py | ||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Line 167: | Line 168: | ||
| Action = Set release status flags to "affected" or "unaffected" based on the status flags in the regressing bug | | Action = Set release status flags to "affected" or "unaffected" based on the status flags in the regressing bug | ||
| Source = regression_set_status_flags.py | | Source = regression_set_status_flags.py | ||
}} | |||
{{BugBotRule | |||
| Rule name = Needinfo triage owner to set severity on bugs | |||
| Purpose = Every defect should have a severity set. Also bugs with no severity set are harder to prioritize for Release Managers with regards to the release (see [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-do-you-triage what-do-you-triage]) | |||
| Action = The triage owner is needinfoed in Bugzilla to set a severity on bugs | |||
| Source = workflow/no_severity_ni.py | |||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Rule name = Nag triage owner to set severity on bugs | | Rule name = Nag triage owner to set severity on bugs | ||
| Purpose = Every defect should have a severity set. Also bugs with no severity set are harder to prioritize for Release Managers with regards to the release (see [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-do-you-triage what-do-you-triage]) | | Purpose = Every defect should have a severity set. Also bugs with no severity set are harder to prioritize for Release Managers with regards to the release (see [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-do-you-triage what-do-you-triage]) | ||
| Action = The triage owner is | | Action = The triage owner is nagged via email to set a severity on bugs | ||
| Source = workflow/no_severity_nag.py | |||
| Source = workflow/ | |||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Line 257: | Line 263: | ||
| Action = Add the missing keywords and needinfo to suggest increasing severity in case of a low severity | | Action = Add the missing keywords and needinfo to suggest increasing severity in case of a low severity | ||
| Source = topcrash_highlight.py | | Source = topcrash_highlight.py | ||
}} | |||
{{BugBotRule | |||
| Rule name = Topcrash notify | |||
| Purpose = Identify topcrash bugs with needinfo without recent activity | |||
| Action = Notify managers and release managers | |||
| Source = topcrash_notify.py | |||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Line 448: | Line 460: | ||
| Action = Add a needinfo request when a bug is moved to Core::Performance to ask for missed information. | | Action = Add a needinfo request when a bug is moved to Core::Performance to ask for missed information. | ||
| Source = moved_to_performance.py | | Source = moved_to_performance.py | ||
}} | |||
{{BugBotRule | |||
| Rule name = Uh-hide duplicate security bugs | |||
| Purpose = Publish security bugs that are already fixed and safe to be public. | |||
| Action = Send emails to people in the security team to highlight security bugs which are duplicates of already-public bugs. | |||
| Source = security_unhide_dups.py | |||
}} | |||
{{BugBotRule | |||
| Rule name = Label WebCompat platform bugs | |||
| Purpose = Ensure core bugs blocking webcompat knowledge base entries have webcompat:platform-bug keyword. | |||
| Action = Add webcompat:platform-bug keyword where it's missing | |||
| Source = webcompat_platform_without_keyword.py | |||
}} | |||
{{BugBotRule | |||
| Rule name = Bugs with the [webcompat:sightline] whiteboard tag updated | |||
| Purpose = Ensure webcompat bugs affecting a sightline top 1000 site have the appropriate keyword set | |||
| Action = Add [webcompat:sightline] whiteboard tag where it's missing, or remove it when it shouldn't be set | |||
| Source = webcompat_sightline.py | |||
}} | |||
{{BugBotRule | |||
| Rule name = Inactive performance regressions | |||
| Purpose = Ensure progress continues on resolving performance regressions. | |||
| Action = Needinfo author of regressor after a period of inactivity. | |||
| Source = perfalert_inactive_regression.py | |||
}} | |||
{{BugBotRule | |||
| Rule name = Performance regression resolution monitoring | |||
| Purpose = Ensure proper resolutions are provided for performance alerts, and request resolution reasoning if needed. | |||
| Action = Needinfo individual who resolved alert when resolution reasoning is not provided, and provide summary emails of resolution changes. | |||
| Source = perfalert_resolved_regression.py | |||
}} | |||
{{BugBotRule | |||
| Rule name = Inactive telemetry alerts | |||
| Purpose = Ensure progress continues on resolving telemetry alerts. | |||
| Action = Needinfo telemetry probe owner after a period of inactivity. | |||
| Source = telemetryalert_inactive_regression.py | |||
}} | |||
{{BugBotRule | |||
| Rule name = web-features links | |||
| Purpose = Ensure bugs marked with a web feature have see-also links to the relevant feature. | |||
| Action = Add see-also links to bugs with `web-feature: <name>` in the user story. | |||
| Source = web_platform_features.py | |||
}} | }} | ||
| Line 494: | Line 548: | ||
| Note = Dropped in favor of [[BugBot#tracked_attention.py|Tracked bugs that need attention]] | | Note = Dropped in favor of [[BugBot#tracked_attention.py|Tracked bugs that need attention]] | ||
}} | }} | ||
{{BugBotRule | |||
| Rule name = Bugs with STR and no regression range | |||
| Purpose = Compleat missing metadata | |||
| Action = Needinfo the bug creator to find the regression range | |||
| Source = has_str_no_range.py | |||
| Removed = yes | |||
| Note = Removed on 2024-02-13 | |||
}} | |||
{{BugBotRule | |||
| Rule name = Nag triage owner to set severity on bugs | |||
| Purpose = Every defect should have a severity set. Also bugs with no severity set are harder to prioritize for Release Managers with regards to the release (see [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-do-you-triage what-do-you-triage]) | |||
| Action = The triage owner is needinfoed in Bugzilla or nagged via email to set a severity on bugs | |||
| Source = workflow/no_severity.py | |||
| Removed = yes | |||
| Note = Split into two rules: [[BugBot#Needinfo_triage_owner_to_set_severity_on_bugs|Needinfo triage owner to set severity on bugs]] and [[BugBot#Nag_triage_owner_to_set_severity_on_bugs|Nag triage owner to set severity on bugs]] | |||
}} | |||
__TOC__ | |||