97
edits
BugBot: Difference between revisions
→Active Rules: Add a section about the inactive telemetry alerts rule.
(→Active Rules: Add a section about the inactive telemetry alerts rule.) |
|||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 263: | 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 466: | Line 472: | ||
| Action = Add webcompat:platform-bug keyword where it's missing | | Action = Add webcompat:platform-bug keyword where it's missing | ||
| Source = webcompat_platform_without_keyword.py | | 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 519: | Line 555: | ||
| Removed = yes | | Removed = yes | ||
| Note = Removed on 2024-02-13 | | 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__ | __TOC__ | ||