66
edits
BugBot: Difference between revisions
Group removed rules in a separate section
(Fix many old typos) |
(Group removed rules in a separate section) |
||
| Line 12: | Line 12: | ||
If you want the bot to not make changes to a specific bug, add <code>[no-nag]</code> to its ''whiteboard'' field. | If you want the bot to not make changes to a specific bug, add <code>[no-nag]</code> to its ''whiteboard'' field. | ||
= Rules = | = Active Rules = | ||
{{BugBotRule | {{BugBotRule | ||
| Rule name = Variant Expiration | | Rule name = Variant Expiration | ||
| Line 167: | Line 167: | ||
| 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 | {{BugBotRule | ||
| Line 238: | Line 230: | ||
| Example = 1620434 | | Example = 1620434 | ||
| Source = uplift_beta.py | | Source = uplift_beta.py | ||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Line 267: | Line 251: | ||
| Example = | | Example = | ||
| Source = inactive_ni_pending.py | | Source = inactive_ni_pending.py | ||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Line 321: | Line 298: | ||
| Purpose = Identify bugs stalled because we need more information from the reporter to reproduce it | | Purpose = Identify bugs stalled because we need more information from the reporter to reproduce it | ||
| Source = reporter_with_ni.py | | Source = reporter_with_ni.py | ||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Line 395: | Line 364: | ||
| Action = Needinfo to propose increasing the severity | | Action = Needinfo to propose increasing the severity | ||
| Source = severity_high_security.py | | Source = severity_high_security.py | ||
}} | }} | ||
{{BugBotRule | {{BugBotRule | ||
| Line 486: | Line 448: | ||
| 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 | ||
}} | |||
= Removed Rules = | |||
{{BugBotRule | |||
| Rule name = Fuzzing bisection without regressed_by | |||
| Purpose = Identify bugs which contain a bisection made by fuzzing tools and an empty regressed_by, probably people forgot to set the field. | |||
| Action = The bug assignee is needinfoed to ask to fill regressed_by when it's possible. | |||
| Example = 1683535 | |||
| Source = fuzzing_bisection_without_regressed_by.py | |||
| Note = Replaced with [[BugBot#bisection_without_regressed_by.py|Bisection without regressed_by]] | |||
}} | |||
{{BugBotRule | |||
| Rule name = Bugs with top-crash signatures | |||
| Purpose = Identify bugs that are missing topcrash or topcrash-startup keywords | |||
| Action = Add the missing keyword and needinfo to suggest increasing severity in case of a low severity | |||
| Source = topcrash_add_keyword.py | |||
| Note = Replaced with [[BugBot#topcrash_highlight.py|Highlight topcrash bugs]] | |||
}} | |||
{{BugBotRule | |||
| Rule name = Top crashers with low severity | |||
| Purpose = Consistency and help getting traction on top-crash bugs | |||
| Action = Needinfo the assignee or the triage owner if not assigned yet | |||
| Example = 1471692 | |||
| Source = topcrash_bad_severity.py | |||
| Note = Replaced with [[BugBot#topcrash_highlight.py|Highlight topcrash bugs]] | |||
}} | |||
{{BugBotRule | |||
| Rule name = Low severity bugs with tracking status | |||
| Purpose = Suggest increasing the severity for bugs that are marked as blocking or are tracked for nightly, beta, or release | |||
| Action = Needinfo the assignee or the triage owner if not assigned yet | |||
| Source = severity_tracked.py | |||
| Note = Dropped in favor of [[BugBot#tracked_attention.py|Tracked bugs that need attention]] | |||
}} | |||
{{BugBotRule | |||
| Rule name = Increase severity of bugs tracked by Release Managers | |||
| Purpose = Fix inconsistency in metadata | |||
| Action = If a bug is tracked for an upcoming release but it's severity field is low, the severity is increased | |||
| Example = 1538966 | |||
| Source = tracked_bad_severity.py | |||
| Note = Dropped in favor of [[BugBot#tracked_attention.py|Tracked bugs that need attention]] | |||
}} | }} | ||