Nagbot might be too eager to cancel needinfos on inactive users (who might really just be "users who have only filed this one bug that's sat untouched for a while")
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Consider this scenario:
https://bugzilla.mozilla.org/show_bug.cgi?id=1767370#c5
- 2022-5-02: User files a bug.
[Bug sat for a few months] - 2022-10-17: jstutte posts a question for the user with a needinfo request.
[User doesn't respond for a couple weeks] - 2022-11-07: autonag bot cancels the needinfo and nags the triage owner instead.
This doesn't seem great. As long as the user's bugzilla account is enabled, we should give them a month or so to respond to a needinfo before bots start to assume that they won't respond. Note that bugzilla sends periodic reminders for needinfos, so they'll get a few nags in case they forget or overlook the first mail.
(From talking to suhaib: it sounds like the triggering event here was that 6 months had just elapsed since the user's last activity, and we take action & cancel needinfo's on the following Monday when that happens. Or something to that effect.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the autonag bot's needinfo-cancellation path described in the issue and review the linked Bugzilla scenario. Trace how the six-month inactivity trigger is applied to enabled users, then compare it with the requested month-long response window. Done means the bot gives these users about a month to answer before cancelling the needinfo and notifying the triage owner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100