Closed Bug 1547598 Opened 6 years ago Closed 4 years ago

"firefox bug husbandry bot" is incorrectly resolving bugs with long-pending needinfo's on developers as incomplete

Categories

(bugzilla.mozilla.org :: Bulk Bug Edit Requests, task, P3)

Product:
bugzilla.mozilla.org
Component:
Bulk Bug Edit Requests
Version:
Production
Type:
task

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: bzbarsky, Assigned: emceeaich)

References

Details

See https://bugzilla.mozilla.org/show_bug.cgi?id=1314422#c3 for an example. This is not us waiting on info from someone outside the org. This is us waiting for info from someone employed to work on Firefox! Closing a bug is NOT the right response if that info does not get provided; prodding the person is.

Apologies if this is filed in the wrong place; neither that comment nor https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry have any contact info listed. :(

And we should probably check for other bugs that got closed for the same reason, given the number of developers we have who treat needinfo as more or less a "backlog todo list" (of which I am as guilty as anyone).

The wiki page has been edited by Emma.

Flags: needinfo?(ehumphries)

This was a one-time pass through bugs with long-term pending needinfos.

The change that needs to be made to the privileged 'no-bugmail' accounts is probably to a send mail to the reporter when the bug is closed so they have the option to reopen the bug.

If there's a pending needinfo, shouldn't the mail go to the source and destination of that needinfo (as well? instead?).

That's a good suggestion.

This should get baked into a "cleanup" method on a closed bug. Should we continue spec'ing that here or do it in a new bug?

Whatever works better for you.

This is still on my "todo" list as part of "closing bugs" process. Hopefully I can work on this in Q1.

Assignee: nobody → ehumphries
Priority: -- → P3

Closing this for now. Discussing bug resolution playbook as 2020H2 goal.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.