3
edits
(→Active Rules: Add WebCompat platform bugs rule) |
|||
| Line 168: | 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 | ||
edits