MozillaWiki

BugBot: Difference between revisions

Page Discussion

BugBot (view source)

Revision as of 18:23, 10 December 2025

18,473 bytes added ,  10 December 2025
→‎Active Rules: Add a section about the inactive telemetry alerts rule.
(→‎Without autofix: Add not_landed.py)
(→‎Active Rules: Add a section about the inactive telemetry alerts rule.)
 
(96 intermediate revisions by 11 users not shown)
Line 1: Line 1:
This page lists all the actions done by the autonag bot.
{{ DISPLAYTITLE:BugBot: Bugzilla triaging bot and alerting system }}


https://github.com/mozilla/relman-auto-nag/tree/master/auto_nag/scripts
<p style="font-size: larger; font-weight:bold;">
This page lists all the actions done by [https://github.com/mozilla/bugbot/ BugBot].</p>


Autofix checkers are executed every hour at *:15. Checkers without autofix are run every day. 14:00 Paris time.
= Introduction =
For now, security bugs aren't touched.
Every day hundreds of tickets are opened in [https://bugzilla.mozilla.org Bugzilla] which track the tasks, defects and enhancements needed for the development of Firefox and other Mozilla projects.
Triaging and prioritizing these bugs are an essential part of our development process and we automate part of this process so as to increase our development turn around and improve the quality of our bugs metadata. The set of tools we use to improve the quality of our bugs, decrease our triaging time and help Release Management ship better quality software is called '''BugBot''' (formerly known as Autonag).


== With autofix ==
Initially created as an alerting system (by email) to our triagers, BugBot rules now also make changes to our bugs metadata on Bugzilla so as to fix inconsistencies.


{|  border="1"
If you want the bot to not make changes to a specific bug, add <code>[no-nag]</code> to its ''whiteboard'' field.
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| '''File'''
|| '''Rules'''
|| '''Why'''
|| '''Has autofix'''
|| '''Example'''
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| assignee_but_unconfirmed.py
|| Change the status from unconfirmed to assigned if there is an assignee
|| Mitigate an issue in bugzilla (bugs reported by new bugzilla users are not tagged as NEW)
|| Yes
|| {{Bug|1495908}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| has_regression_range_no_keyword.py
|| Regression range = yes has been set but missing keyword
|| Regression keyword is important to differentiate actual defect
|| Yes
|| {{Bug|1461034}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| leave_open.py
|| Remove the leave-open keyword on bug closed
|| Mismatch in metadata
|| Yes
|| {{Bug|1382185}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| meta_summary_missing.py
|| Has [meta] in the description but not the keyword
|| Keyword helps a lot in search
|| Yes
|| {{Bug|1435799}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| nightly_reopened.py
|| If a bug is reopened in nightly, the status flags aren’t automatically updated
|| Avoids some potential issues for sheriff and release managers
|| Yes
|| {{bug|1495962}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| no_assignee.py
|| no assignees and a patch which landed in m-c
|| Bugs without assignee is making our life harder
|| Yes
|| {{bug|1514338}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| no_crashes.py
|| Crash bugs without any crash reports for more than 12 weeks
|| Mitigate the backlog
|| Yes
|| {{bug|1470864}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| stalled.py
|| But closed but has the stalled keyword
|| If the bug is closed, it isn't stalled anymore
|| Yes
|| {{bug|1491624}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| summary_meta_missing.py
|| Has the meta keyword but [meta] is missing in the description
|| Having [meta] in the summary help with search of bugs
|| Yes
|| {{bug|1257692}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| missing_beta_status.py
|| Status flags are set for nightly and release but not for beta
|| Inconsistency in status flags
|| Yes
|| {{bug|1500273}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| mismatch-priority-tracking-*.py
|| If a bug is tracked by a release manager, update the priority (P2 for nightly, P1 for the rest)
|| Show that it is important
|| Yes
|| {{bug|1515946}} / {{bug|1508277}} / {{bug|1512493}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| regression.py
|| Bug without the regression keyword
|| Regression keyword is important to differentiate actual defect. Uses machine learning
|| Yes
|| {{bug|1529139}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| component.py
|| Bug in untriaged
|| Move the bug into the right component. Uses machine learning
|| Yes
|| {{bug|1530316}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
|| copy_duplicate_info.py
|| Bug resolved as duplicate
|| Copy crash signatures from dup bug to original bug and copy product/component from original to dup.
|| Yes
|| {{bug|1517205}}
|-
|}


== Without autofix ==
= Active Rules =
{| border="1"
{{BugBotRule
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
  | Rule ID  = 163
|| '''File'''
  | Rule name = Variant Expiration
|| '''Rules'''
  | Purpose  = Follow up on variants that need to be dropped or extended
|| '''Why'''
  | Action    = Create a bug before the variant becomes expired and follow up to extend or drop it
|| '''Has autofix'''
  | Source    = variant_expiration.py
|| '''Example'''
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| feature_regression.py
  | Rule name = Detect spam bugs
|| the bug with both feature and regression keywords
  | Purpose  = Automatically detect and handle spam bugs
|| Mismatch in metadata
  | Action    = Close the bug as "INVALID" and move it to the "Invalid Bugs" product
|| No
  | Source    = spambug.py
||
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| leave_open_no_activity.py  
  | Rule name = File bugs for new actionable crashes
|| Has the leave-open keyword but no activity for a while
  | Purpose  = Automate discovering actionable crash reports to speed up fixes, reduce user impact, and save engineering time.
|| Help identify dead/inactive bugs
  | Action    = Open a crash bug with the relevant information
|| Needinfo to triage owner
  | Source    = file_crash_bug.py
|| {{Bug|1367072}}
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| meta_no_deps_no_activity.py  
  | Rule name = Wrong bug type
|| Meta bug without open dependencies and no activity
  | Purpose  = Correct the bug type
|| Help identify dead/inactive bugs
  | Action    = Check if the bug type is the same as predicted by bugbug, if it is different and the bot is confident, correct the type
|| Needinfo to triage owner
  | Source    = defectenhancementtask.py  
||
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| mismatch-priority-tracking.py
  | Rule name = Enhancement or task with the "regression", "crash" or "assertion" keyword
|| A bug is tracked by release management but the severity is small (<normal)
  | Purpose  = Correct the bug type
|| Mismatch in metadata
  | Action    = Change the bug type to "defect"
|| No
  | Source    = regression_but_type_enhancement_task.py
||
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| ni_from_manager.py
  | Rule name = Closed bugs with dupeme keyword
|| Bugs with a ni from a director or a release manager and no activity
  | Purpose  = Clean up the metadata
|| We need to have fast turn around on bugs
  | Action    = Remove the dupeme keyword
|| Mail
  | Source    = closed_dupeme.py  
||
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| ni_triage_owner.py
  | Rule name = Bugs with dupeme in the whiteboard instead of keyword
|| Bugs with no priority and no activity
  | Purpose  = Clean up the metadata
|| Triage owners need to process the backlog
  | Action    = Replace the '[dupeme]' whiteboard tag with the 'dupeme' keyword
|| Needinfo to triage owner (only Andrew for now)
  | Source    = dupeme_whiteboard_keyword.py
|| {{bug|1503461}}
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| one_two_word_summary.py  
  | Rule name = Bugs with no 'Has STR' and STR in the first comment
|| Bugs with only one or two words in the summary
  | Purpose  = Compleat missing metadata
|| usually a sign of an useless bug
  | Action    = Set the 'Has STR' field to be 'yes'
|| No
  | Source    = has_str_no_hasstr.py
|| {{bug|1512823}}
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| query_creator.py  
  | Rule name = Copy metadata from duplicates
|| Send reminders to developer with assigned tracked bugs
  | Purpose  = Increase the visibility of important information after closing a bug as a duplicate
|| Make sure that bugs for the next release are addressed
  | Action    = Copy missed metadata from duplicate bugs
|| No
  | Source    = duplicate_copy_metadata.py
||
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| reporter_with_ni.py
  | Rule name = Bugs with small crash volume
|| Identify bugs with needinfo on the reporter without activity
  | Purpose  = Identify topcrash or high severity bugs that started getting small crash volume
|| Usually a sign of a reporter not answering to more requests
  | Action    = Remove the topcrash keywords and decrease the bug severity if the crash volume is very low
|| No
  | Source    = crash_small_volume.py
||
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| topcrash_bad_severity.py  
  | Rule name = Bugs with higher severity duplicates
|| Topcrash bugs with normal severity
  | Purpose  = Highlight inconsistency in the severity between a bug and its duplicates
|| Consistency and help getting traction on bugs
  | Action    = Needinfo the assignee and fallback to the triage owner if a duplicate bug has a higher severity value
|| No
  | Source    = severity_higher_dups.py  
|| {{bug|1471692}}
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| tracked_bad_severity.py
  | Rule name = Regression on nightly
|| Bug tracked by release managers but small severity
  | Purpose  = Increase the visibility of regression bugs
|| Inconsistency in metadata
  | Action    = Set nightly status flag to affected on newly filed regression bugs
|| No
  | Source    = regression_new_set_nightly_affected.py
||
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| tracked_needinfo.py  
  | Rule name = Remove <code>leave-open</code> keyword on closed bug
|| Tracked or Nominated for Tracking with Need-Info?
  | Purpose  = Clean up a mismatch in metadata
|| Make sure that bugs for the next release are addressed
  | Action    = If a bug is closed but the <code>leave-open</code> keyword is still set, remove it
|| Email
  | Example  = 1382185
||
  | Source    = leave_open.py  
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
}}
|| tracking.py
{{BugBotRule
|| Get the tracked bugs in a release and untouched this week
  | Rule name = [meta] in title but not in keywords
|| Identify inactive bugs
  | Purpose  = Improve metedata quality
|| Email
  | Action    = Adds the <code>meta</code> keyword if the bug title starts by [META]
||  
  | Example  = 1435799
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
  | Source    = meta_summary_missing.py
|| unaffected_affected_no_reg.py  
}}
|| List bugs marked as non affecting a release but affecting the next one
{{BugBotRule
|| Sign of a regression
  | Rule name = Update Firefox Status flags for bugs reopened during Nightly cycle
|| Email
  | Purpose  = Avoids potential issues for sheriffs and release managers
||
  | Action    = Set <code>firefox-status</code> flag back from ''fixed'' to ''affected''
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
  | Example  = 1495962
|| unlanded.py
  | Source    = nightly_reopened.py
|| Patches which didn’t land on beta and esr
}}
|| Make sure that we ship with the bugs that we need
{{BugBotRule
|| Email
  | Rule name = Bug with no assignee but a patch landed
|| {{bug|1509394}}
  | Purpose  = Attribute unassigned bug to the developer that fixed it
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
  | Action    = The ASSIGNEE field on the bug is changed from nobody@mozilla.org to the author of the patch that landed in mozilla-central
|| untriage_important_sev.py
  | Example  = 1514338
|| Firfox/untriaged with an important severity
  | Source    = no_assignee.py
|| Identify potential important issues in untriage
}}
||
{{BugBotRule
||
  | Rule name = Close crash bugs with no crashes over 12 weeks
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
  | Purpose  = Reduce the backlog of bugs to check for Release Managers
|| version_affected.py
  | Action    = Crash bugs without any crash reports for more than 12 weeks
|| Bug with version set but not status_firefox
  | Example  = 1470864
|| Version is set automatically by bugzilla but status_firefox isn’t
  | Source    = no_crashes.py
|| Email
}}
||
{{BugBotRule
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
  | Rule name = Remove <code>stalled</code> keyword on closed bugs
|| ../next_release.py
  | Purpose  = Fix inconsistency between metadata and bug status
|| Check if the release dates are consistent on the Wiki pages
  | Action    = If a bug is marked as <code>FIXED</code> and also has a <code>stalled</code> keyword set, the keyword is removed
|| We use these dates in automation
  | Example  = 1491624
|| Email
  | Source    = stalled.py
||
}}
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
{{BugBotRule
|| code_freeze_week.py
  | Rule name = Has meta keyword but not [meta] in the bug title
|| Fixed bug with patches which landed in mozilla-central during the soft freeze week
  | Purpose  = Having [meta] in the bug title helps with quick search results
|| Give some information like number of patches, number of changed lines, ...
  | Action    = If a bug has the meta keyword set, [meta] is added to the bug title
|| Email
  | Example  = 1257692
||
  | Source    = summary_meta_missing.py
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
}}
|| missed_uplifts.py
{{BugBotRule
|| Fixed bug in nightly with patches and beta or release affected.
  | Rule name = Set a Firefox status flag for beta if there is one for nightly and release
|| Give some information about priority, severity, ...
  | Purpose  = Fix inconsistency in Firefox status flags that can lead to a bug going undetected by Release Managers during the beta cycle
|| Email
  | Action    = If a status exists for Firefox N-1 and for Firefox N+1, guess a value for Firefox N
||
  | Example  = 1500273
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
  | Source    = missing_beta_status.py
|| newbie_with_ni.py
}}
|| Bug where the reporter has a needinfo and with no activity
{{BugBotRule
|| Help to identify probably unactionnable bugs because of lack of information
  | Rule name = Add <code>regression</code> keywords to bugs (uses Machine Learning)
|| Email
  | Purpose  = Surface regressions not filed as such
||
  | Action    = If a bug is tracked by a Release Manager, update the priority (P2 for nightly, P1 for the rest)
|- style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.053cm;padding-right:0.053cm;"
  | Example  = 1529139
|| not_landed.py
  | Source    = regression.py  
|| Bug with a r+ patch but the patch didn't land.
}}
|| Maybe a checkin-needed is required or the patch is obsolete
{{BugBotRule
|| Email
  | Rule name = Move untriaged bug into the correct component (uses machine learning) 
||
  | Purpose  = Decrease manual triage time
  | Action    = Uses machine learning to mass move bugs in Firefox::Untriaged into a better component
  | Example  = 1530316
  | Source    = component.py
}}
{{BugBotRule
  | Rule name = Copy crash signature from duplicate bugs to main bugs
  | Purpose  = Crash bugs marked as duplicate of another one may have a different crash signature. We need to consolidate all signatures in the bug where a patch to fix them is being worked on, other wise we may not fix them all
  | Action    = If a crash bug is marked as a duplicate, the signatures it referenced are added to the new bug
  | Example  = 1517205
  | Source    = copy_duplicate_info.py
}}
{{BugBotRule
  | Rule name = Update release status flags based on info from the regressing bug
  | Purpose  = Automate setting the release status flags
  | Action    = Set release status flags to "affected" or "unaffected" based on the status flags in the regressing bug
  | 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
  | 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 nagged via email to set a severity on bugs
  | Source    = workflow/no_severity_nag.py
}}
{{BugBotRule
  | Rule name = Nag triage owner on P1 bugs with no activity
  | Purpose  = Since P1 means that the bug should be fixed for the next release (see [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-do-you-triage what-do-you-triage]), the bug needs to show any progress in its resolution (or maybe the priority should be decreased)
  | Action    = The triage owner is nagged via email to have a reminder
  | Example  = 1507251
  | Source    = workflow/p1_no_activity.py
}}
{{BugBotRule
  | Rule name = Nag triage owner to find an assignee for P1 bugs with no assignee and no activity
  | Purpose  = Since P1 means that the bug should be fixed for the next release (see [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-do-you-triage what-do-you-triage]), the bug urgently needs to have an assignee (or the priority should be decreased)
  | Action    = The triage owner is needinfoed in Bugzilla or nagged via email to find an assignee on bugs
  | Example  = 1541291
  | Source    = workflow/p1_no_assignee.py
}}
{{BugBotRule
  | Rule name = Change the priority from P2 to P1 on assigned bug the merge day
  | Purpose  = Since P2 means that the bug should be fixed for the next release (see [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-do-you-triage what-do-you-triage]), when we are the merge day then this bug automatically becomes a P1.
  | Action    = Update the priority to P1 and add a comment to explain.
  | Example  =
  | Source    = workflow/p2_merge_day.py
}}
{{BugBotRule
  | Rule name = Patch not landed
  | Purpose  = Identify bugs with an unlanded r+ patch. Maybe the patch is now obsolete or the bug needs to have a sheriff land the code with the <code>checkin-needed</code> keyword set.
  | Action    = The bug assignee is needinfoed in Bugzilla to ask her/him to have a look
  | Example  = 1496844
  | Source    = not_landed.py
}}
{{BugBotRule
  | Rule name = Regression without regressed_by and some bug dependencies
  | Purpose  = Identify regressions which have dependencies (blocks or depends_on) and an empty regressed_by, probably people forgot to use the new field.
  | Action    = The bug assignee or the person who added some dependencies or the reporter is needinfoed to ask to fill regressed_by when it's possible.
  | Example  = 1545797
  | Source    = regression_without_regressed_by.py
}}
{{BugBotRule
  | Rule name = Product::Component changed after the priority has been set
  | Purpose  = Identify bugs where Product::Component changed after the priority has been set. The priority is probably no more up-to-date and so triage owner needs to set it.
  | Action    = Reset the priority to "--" with a comment explaining why the bot is doing that.
  | Example  = 1546366
  | Source    = prod_comp_changed_with_priority.py
}}
{{BugBotRule
  | Rule name = Close intermittent test failure bugs
  | Purpose  = Close intermittent test failure bugs which are P5s, not marked <code>leave-open</code>, and have not had a new failure in 21 days.
  | Action    = RESOLVE bug as INCOMPLETE with a comment explaining why the bot is doing this.
  | Example  = 1577895
  | Source    = close_intermittents.py
}}
{{BugBotRule
  | Rule name = Ask for a beta uplift request
  | Purpose  = Identify bugs where a patch fixed a bug in nightly and beta is marked as affected.
  | Action    = Needinfo the assignee to ask it's worth making an uplift request.
  | Example  = 1620434
  | Source    = uplift_beta.py
}}
{{BugBotRule
  | Rule name = Bisection without regressed_by
  | Purpose  = Identify bugs which contain a bisection made by mozregression or fuzzing tools and an empty regressed_by, probably people forgot to set the field.
  | Action    = The bug assignee or the regression author is needinfoed to ask to fill regressed_by when it's possible.
  | Example  = 1683535
  | Source    = bisection_without_regressed_by.py
}}
{{BugBotRule
  | Rule name = Unassign inactive bugs with the good-first-bug keyword
  | Purpose  = Identify inactive good first bugs, to free them up for other contributors.
  | Action    = Reset the assignee and status fields and post a comment.
  | Example  =
  | Source    = good_first_bug_unassign_inactive.py
}}
{{BugBotRule
  | Rule name = Bugs with needinfo requests on inactive people
  | Purpose  = Identify bugs that have pending needinfo on inactive users.
  | Action    = Depending on the bug, redirect the needinfo to the triage owner, cancel the needinfo, or close the bug.
  | Example  =
  | Source    = inactive_ni_pending.py
}}
{{BugBotRule
  | Rule name = Highlight topcrash bugs
  | Purpose  = Identify topcrash bugs that are missing topcrash keywords or have low severity
  | Action    = Add the missing keywords and needinfo to suggest increasing severity in case of a low severity
  | 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
  | Rule name = Approve tracking request for expiring telemetry
  | Purpose  = Save time and eliminate unnecessary manual work
  | Action    = Automatically approve tracking requests for bugs created by <code>telemetry-probes@mozilla.bugs</code>
  | Source    = telemetry_expiry_tracking_autoapproval.py
}}
{{BugBotRule
  | Rule name = Feature vs regression
  | Purpose  = Fix inconsistency in bugs with both the <code>regression</code> and <code>feature</code> keywords set
  | Source    = feature_regression.py
}}
{{BugBotRule
  | Rule name = Inactive bugs with the <code>leave-open</code> keyword set
  | Purpose  = Help identify dead/inactive bugs
  | Action    = Needinfo the triage owner if a bug is inactive but has the <code>leave-open</code> keyword set
  | Example  = 1367072
  | Source    = leave_open_no_activity.py
}}
{{BugBotRule
  | Rule name = Inactive Meta bugs
  | Purpose  = Help identify dead/inactive bugs
  | Action    = Needinfo the triage owner if a meta bug has no activity and no dependencies set
  | Source    = meta_no_deps_no_activity.py
}}
{{BugBotRule
  | Rule name = Alert for lack of feedback in a bug
  | Purpose  = Increase reaction time on bugs prioritized by upper management or release managers
  | Action    = If a bug has an unanswered needinfo request from a release manager or a director, send a warning email
  | Source    = ni_from_manager.py
}}
{{BugBotRule
  | Rule name = Bugs with only one or two words in the summary
  | Purpose  = Make sure the bug is actually useful, a two-words summary often indicates a poor quality bug report
  | Example  = 1512823
  | Source    = one_two_word_summary.py
}}
{{BugBotRule
  | Rule name = Reporter not answering to Needinfo request
  | Purpose  = Identify bugs stalled because we need more information from the reporter to reproduce it
  | Source    = reporter_with_ni.py
}}
{{BugBotRule
  | Rule name = Identify tracked bugs with a NeedInfo request
  | Purpose  = Make sure that bugs tracked for a release or nominated for tracking which also have a NeedInfo request do not get stuck
  | Action    = Send an email
  | Source    = tracked_needinfo.py
}}
{{BugBotRule
  | Rule name = Tracked bugs untouched for a week
  | Purpose  = Identify important bugs for a release which are not being acted upon
  | Action    = Send an email
  | Source    = tracking.py
}}
{{BugBotRule
  | Rule name = Identify unlanded uplifts to Beta and ESR
  | Purpose  =  Make sure that we ship with the bugs that we need
  | Action    = Send an email wih the list of bugs with uplift requests not landed on the affected branch
  | Example  = 1509394
  | Source    = unlanded.py
}}
{{BugBotRule
  | Rule name = Bugs with high severity in Firefox::Untriaged
  | Purpose  = Identify potentially important issues left untriaged
  | Source    = untriage_important_sev.py
}}
{{BugBotRule
  | Rule name = Information about bugs landed during Soft Code Freeze
  | Purpose  = List fixed bug with patches  which landed in mozilla-central during the soft freeze week. The listing includes patch statistics.
  | Action    = Send an email
  | Source    = code_freeze_week.py
}}
{{BugBotRule
  | Rule name = Hightlight Fixed bugs in nightly we may want to uplift
  | Purpose  = Identify potentially upliftable  bugs.
  | Action    = Send an email with the recent fixes, the affected branches and metadata for prioritization
  | Source    = missed_uplifts.py
}}
{{BugBotRule
  | Rule name = New user with a Needinfo request
  | Purpose  = Help identify potentially unactionable bugs per lack of information
  | Action    = Send an email
  | Source    = newbie_with_ni.py
}}
{{BugBotRule
  | Rule name = Assignee is inactive
  | Purpose  = Help identify bugs that are assigned to inactive accounts
  | Action    = Reset the assignee, and if the bug has high priority or high severity, needinfo the triage owner
  | Source    = assignee_no_login.py
}}
{{BugBotRule
  | Rule name = Bugs with inconsistent severity flags
  | Purpose  = Make sure that bugs severity is consistent with the [[Accessibility/Triage#Triaging_Firefox_and_Gecko_feature_defects|accessibility severity]] on the Whiteboard
  | Action    = Needinfo the assignee or the triage owner if not assigned yet
  | Source    = severity_inconsistency.py
}}
{{BugBotRule
  | Rule name = Regression bugs where the regressor author is not involved
  | Purpose  = Highlight regressions to people who caused them
  | Action    = Needinfo the assignee of the bug that caused the regression
  | Source    = needinfo_regression_author.py
}}
{{BugBotRule
  | Rule name = Bugs with high security keywords which are set to low severity
  | Purpose  = Identify bugs whose severity field is set to S3 or S4 and at the same time have sec-high or sec-critical keywords
  | Action    = Needinfo to propose increasing the severity
  | Source    = severity_high_security.py
}}
{{BugBotRule
  | Rule name = Bugs with P1 WebCompat priority and severity set to low
  | Purpose  = Consistency and getting traction on important web compatibility bugs
  | Action    = Needinfo the assignee or the triage owner if not assigned yet
  | Source    = severity_high_compat_priority.py
}}
{{BugBotRule
  | Rule name = Automatically confirm bugs that have an affected Firefox version flag
  | Purpose  = Fix inconsistency in the status of unconfirmed bugs
  | Action    = Confirm bugs with affected Firefox version flags by changing the status to "NEW"
  | Source    = affected_flag_confirm.py
}}
{{BugBotRule
  | Rule name = Automatically confirm bugs that have a crash signature
  | Purpose  = Fix inconsistency in the status of unconfirmed bugs
  | Action    = Confirm bugs with crash signatures by changing the status to "NEW"
  | Source    = crash_signature_confirm.py
}}
{{BugBotRule
  | Rule name = Bugs with patches after being closed
  | Purpose  = Identify bugs that receive patches after being closed
  | Action    = Comment on the bug and email release managers
  | Source    = patch_closed_bug.py
}}
{{BugBotRule
  | Rule name = Bugs with underestimated severity levels
  | Purpose  = Identify bugs whose severity could be underestimated
  | Action    = Needinfo the assignee or the triage owner if not assigned yet
  | Source    = severity_underestimated.py
}}
{{BugBotRule
  | Rule name = Components with triage owner need to be assigned
  | Purpose  = Identify components whose triage owners are unassigned, disabled, or inactive
  | Action    = Nag managers to assign triage owners
  | Source    = vacant_triage_owner.py
}}
{{BugBotRule
  | Rule name = Tracked bugs that need attention
  | Purpose  = Notify about tracked bugs with no assignee, low severity, or low priority
  | Action    = Needinfo the team manager and fallback on the triage owner if we have no team manager defined in our config
  | Source    = tracked_attention.py
}}
{{BugBotRule
  | Rule name = Bugs with inactive patch reviewers
  | Purpose  = Unblock bugs by identifying patches that are waiting for review from or unavailable reviewers
  | Action    = Needinfo patch authors to find active reviewers
  | Source    = inactive_reviewer.py
}}
{{BugBotRule
  | Rule name = Fuzz blocker bugs
  | Purpose  = Bring attention to bugs that prevent fuzzing from making progress
  | Action    = Send weekly reminder emails and suggest increasing the severity when it is low.
  | Source    = fuzz_blockers.py
}}
{{BugBotRule
  | Rule name = Severity of performance impacting bugs
  | Purpose  = Consistency and help getting traction on bugs with a high impact on performance
  | Action    = Needinfo the assignee or the triage owner (if not assigned) to increase the severity
  | Source    = severity_high_performance_impact.py
}}
{{BugBotRule
  | Rule name = Bugs with a high number of recent regressions
  | Purpose  = Highlight bugs that introduce a high number of regressions
  | Action    = Notify release managers
  | Source    = warn_regressed_by.py
}}
{{BugBotRule
  | Rule name = Bugs with whiteboard reminders
  | Purpose  = Remind about future tasks
  | Action    = Post a reminder on the bug and remove the reminder whiteboard tag
  | Source    = reminder.py
}}
{{BugBotRule
  | Rule name = Bugs to triage
  | Purpose  = Highlight defect bugs that need to be triaged
  | Action    = Notify the triage owner
  | Source    = to_triage.py
}}
{{BugBotRule
  | Rule name = Bugs moved to Core::Performance
  | Purpose  = Make sure the bug has the basic information needed for performance bugs.
  | Action    = Add a needinfo request when a bug is moved to Core::Performance to ask for missed information.
  | 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
}}
 
= 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
  | Removed  = yes
  | 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
  | Removed  = yes
  | 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
  | Removed  = yes
  | 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
  | Removed  = yes
  | 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
  | Removed  = yes
  | 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__
Gmierz
97

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1208782...1255949"