Closed Bug 1453539 Opened 7 years ago Closed 6 years ago

Start running script to resolve open bugs without activity in at least a year as INACTIVE

Categories

(bugzilla.mozilla.org :: Administration, task, P2)

Product:
bugzilla.mozilla.org
Component:
Administration
Version:
Production
Type:
task

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: emceeaich, Assigned: dylan)

References

Details

User Story

Mark all bugs matching this query as RESOLVED INACTIVE. 

This is all unresolved, non-P1 bugs with no activity in at least a year in the Firefox-related components.

Revised query:
f1=days_elapsed&f2=priority&f3=bug_id&f4=reporter&list_id=14163055&n4=1&o1=greaterthan&o2=notequals&o3=greaterthan&o4=equals&product=Core&product=External Software Affecting Firefox&product=Firefox&product=Firefox for Android&product=Firefox for iOS&product=NSPR&product=NSS&product=Toolkit&query_format=advanced&resolution=---&v1=365&v2=P1&v3=0&v4=intermittent-bug-filer%40mozilla.bugs&order=bug_id DESC&limit=0

The comment to apply the bugs is:

"Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened."

There'll be a followup for triage owners to review the P1 bugs with no changes in a year.

Attachments

(1 obsolete file)

Attached file Node script to resolve bugs (obsolete) (deleted) —
Adding first version of script. Will ask for review in GitHub
Where was this error message from? { documentation: 'http://www.bugzilla.org/docs/4.2/en/html/api/', error: true, code: 100500, message: 'DBD::mysql::db do failed: Deadlock found when trying to get lock; try restarting transaction [for Statement "INSERT IGNORE INTO profiles_statistics_recalc SET user_id=?"] at /app/extensions/UserProfile/Extension.pm line 174.\n' }
Assignee: nobody → ehumphries
Priority: -- → P2
(In reply to Dylan Hardison [:dylan] (he/him) from comment #3) > Where was this error message from? > > { documentation: 'http://www.bugzilla.org/docs/4.2/en/html/api/', > error: true, > code: 100500, > message: 'DBD::mysql::db do failed: Deadlock found when trying to get > lock; try restarting transaction [for Statement "INSERT IGNORE INTO > profiles_statistics_recalc SET user_id=?"] at > /app/extensions/UserProfile/Extension.pm line 174.\n' } On mozilla-dev testing the script on a sub-set of bugs.
Comment on attachment 8967238 [details] Node script to resolve bugs Not too keen on the console.log instances. They should typically be avoided.
Attachment #8967238 - Flags: review?(mdaly) → review-
Comment on attachment 8967238 [details] Node script to resolve bugs agree with mdaly's r-, sorry for the delay.
Attachment #8967238 - Flags: review?(dylan) → review-
What should I be using instead of console log for a command line script?
Flags: needinfo?(mdaly)
(In reply to Emma Humphries, Bugmaster ☕️ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #8) > What should I be using instead of console log for a command line script? off the top of my head I would use this: https://nodejs.org/api/process.html#process_process_stdout But it's been awhile since I made a strictly cli nodejs app. I typically suggest avoiding writing directly to the console. You'll want to save data to a file (or db) and then display that.
Flags: needinfo?(mdaly)
Let's run this using Dylan's console script as the admin user. I'll update the user story with the query details and messages.
User Story: (updated)
Also in case there are questions, we can direct people to this: We are adding a new resolution, INACTIVE which will be applied to any bug in the Core, Firefox, Firefox for Android, Firefox for iOS, NSS, NPSR, and Toolkit products which have had no new activity in a year. Q: Why are we doing this? A: So we can focus on current, active bugs. So we can accurately talk about the state of bugs in Firefox. Older, inactive bugs may not even be relevant to current Firefox because of changes to the product. Q: Does this mean you don't care about bugs filed by the community? A: No, these are bugs without activity in at least a year. We are constantly reviewing new bugs, and there are dedicated triage leads on the Firefox team responsible for making decisions on new bugs. Q: What about my bug? A: If a bug you filed is resolved as INACTIVE, and is not a feature request, and applies to a currently supported version of Firefox, you may reopen it. However, mass re-openings because you disagree with the maintainer's decision will be treated as a violation of our Community Participation Guidelines. Q: What about a bug marked INACTIVE but with un-reviewed or un-merged patches? A: Depending on the age of the patch it may not be applicable, and probably not merge-able without editing. If there's a bug with a patch you'd like to be considered, reopen it. If you can do some work to see if the patch can still be applied, it will make the job easier. Q: Nobody else does this! A: The Chromium project does do this. See https://www.chromium.org/issue-tracking/autotriage.
Assignee: ehumphries → dylan
I'm using a slightly different query -- with the number of days set to 365 and excluding tree herder bot. I'll run it a second time on just tree herder bot if that's desired, but first I think the non-treeherder bot bugs are more important.
User Story: (updated)
This will take a long time. Perhaps days. But it has begun.
The content of attachment 8967238 [details] has been deleted for the following reason: Obsolete
Hello, I posted a few concerns and questions in the firefox-dev mailing list, could you please have a look? Thank you.
Hey! When normal users file bugs, they're first taken to a "Find similar issues" text entry, and that field will find INACTIVE bugs. As for the other issues raised in that post, I'll wait for Emma to respond. But I think this is a reasonable thing to do.
Depends on: 1464198
The process is paused with 7008 bugs remaining. Let me know when it should
No longer blocks: bmo-undo-inactive
See Also: → bmo-undo-inactive
Depends on: 1464331
This looks stalled and I don't understand my previous comment. Emma, what should be done here?
Flags: needinfo?(ehumphries)
Marking as incomplete.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(ehumphries)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: