BugBot: Difference between revisions

{{ DISPLAYTITLE:Autonag, our bugzilla automatic triage bot and alerting system }}

This page lists all the actions done by the [https://github.com/mozilla/relman-auto-nag/tree/master/auto_nag/scripts Autonag bot].</p>

Autofix checkers are executed every hour at *:15. Checkers without autofix are run every day. 14:00 Paris time. ''For now, security bugs aren't touched.''

{| class="wikitable"

{|  class="wikitable"

|-  

! File

! Rules

! Why

! Example

|-  

| feature_regression.py  

| the bug with both feature and regression keywords

| Mismatch in metadata

| Not yet

|

|-

| leave_open_no_activity.py  

| Has the leave-open keyword but no activity for a while

| Help identify dead/inactive bugs

| Needinfo to triage owner

| {{Bug|1367072}}

|-

| meta_no_deps_no_activity.py  

| Meta bug without open dependencies and no activity

| Help identify dead/inactive bugs

| Needinfo to triage owner

|

|-

| mismatch-priority-tracking.py  

| A bug is tracked by release management but the severity is small (<normal)

| Mismatch in metadata

| Not yet

|  

|-

| ni_from_manager.py  

| Bugs with a ni from a director or a release manager and no activity

| We need to have fast turn around on bugs

| Mail

|  

|-

| ni_triage_owner.py  

| Bugs with no priority and no activity

| Triage owners need to process the backlog

| Needinfo to triage owner (only Andrew for now)

| {{bug|1503461}}

|-

| one_two_word_summary.py  

| Bugs with only one or two words in the summary

| usually a sign of an useless bug

| Not yet

| {{bug|1512823}}

|-

| query_creator.py  

| Send reminders to developer with assigned tracked bugs  

| Make sure that bugs for the next release are addressed

| Not yet

|  

|-

| reporter_with_ni.py  

| Identify bugs with needinfo on the reporter without activity

| Usually a sign of a reporter not answering to more requests

| Not yet

|

|-  

| topcrash_bad_severity.py  

| Topcrash bugs with normal severity

| Consistency and help getting traction on bugs

| Not yet

| {{bug|1471692}}

|-

| tracked_needinfo.py  

| Tracked or Nominated for Tracking with Need-Info?

| Make sure that bugs for the next release are addressed

| Email

|  

|-

| tracking.py  

| Get the tracked bugs in a release and untouched this week

| Identify inactive bugs

| Email

|  

|-

| unaffected_affected_no_reg.py  

| List bugs marked as non affecting a release but affecting the next one

| Sign of a regression

| Email

|  

|-

| unlanded.py  

| Patches which didn’t land on beta and esr

| Make sure that we ship with the bugs that we need

| Email

| {{bug|1509394}}

|-

| untriage_important_sev.py  

| Firfox/untriaged with an important severity

| Identify potential important issues in untriage

| Not yet

|  

|-

| version_affected.py  

| Bug with version set but not status_firefox

| Version is set automatically by bugzilla but status_firefox isn’t

| Email  

|

|-

| ../next_release.py

| Check if the release dates are consistent on the Wiki pages

| We use these dates in automation

| Email

|

|-

| code_freeze_week.py

| Fixed bug with patches which landed in mozilla-central during the soft freeze week

| Give some information like number of patches, number of changed lines, ...

| Email

|

|-

| missed_uplifts.py

| Fixed bug in nightly with patches and beta or release affected.

| Give some information about priority, severity, ...

| Email

|

|-

| newbie_with_ni.py

| Bug where the reporter has a needinfo and with no activity

| Help to identify probably unactionnable bugs because of lack of information  

| Email

|

|-

| not_landed.py

| Bug with a r+ patch but the patch didn't land.

| Maybe a checkin-needed is required or the patch is obsolete  

| Email

|

|}

 

[[category:Release_Management|Autonag]]