old Needs-Feedback bugs aren't being Archived |
||||
Issue descriptionWe noticed during a triage today that old Needs-Feedback bugs aren't being auto-archived. According to the docs at https://www.chromium.org/issue-tracking/autotriage#TOC-Needs-Feedback-bugs-where-feedback-is-not-received-for-more-than-30-days, sheriffbot should be auto-archiving these after 30 days of no activity. Here's a link showing old Needs-Feedback bugs (showing 1480 bugs as of 10/3): https://bugs.chromium.org/p/chromium/issues/list?can=2&q=modified%3Ctoday-31+Needs%3DFeedback+&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids
,
Oct 12
Hi, we (Chrome Storage) took a look today and noticed this bug was still happening. It looks like there's +13 bugs in the query as of 10/12 (total 1493). Is it possible this is a quick fix, like a cronjob that got turned off by accident?
,
Oct 12
It looks like for the bugs we saw there wasn't a single problem re: Needs-Feedback. Here's a summary of the issues we found after a brief review: Issue 875166 (https://bugs.chromium.org/p/chromium/issues/detail?id=875166): Aug 20 2018 - Needs-Feedback added, no updates since then -> No feedback in last 30 days, bug should be auto-archived Issue 485687 (https://bugs.chromium.org/p/chromium/issues/detail?id=485687) Dec 17 2016 - Needs-Feedback added Dec 17 2016 - Feedback received -> Sheriffbot should have removed Needs-Feedback on Dec 17 2016, bug should not be auto-archived Issue 801979 (https://bugs.chromium.org/p/chromium/issues/detail?id=801979): Jan 17 2018 - Needs-Feedback added Jan 17 2018 - Feedback received Jan 17 2018 - sheriffbot removed Needs-Feedback Jan 18 2018 - Needs-Feedback added by a Chromium project member Jan 18 2018 - Same Chromium project member adds a new label (so should not count as feedback) -> No feedback in last 30 days, bug should be auto-archived
,
Nov 8
1568 Needs-Feedback bugs now.
,
Dec 7
jeffcarp@: We discussed this in person a few weeks ago. Sorry I forgot to add you earlier! Can you please let us know if this will get fixed, or if we should assume the bot is unreliable and move our workflow away from using Needs-Feedback labels?
,
Dec 13
This sounds like a Sheriffbot issue and it looks like the right component is Tools>Stability>SheriffBot in /p/chromium. Moving there.
,
Dec 13
,
Dec 13
,
Jan 10
Issue moved from a project with a different set of status labels. "New" is not a supported status in /p/chromium, so these ended up in a black-hole. |
||||
►
Sign in to add a comment |
||||
Comment 1 by jojwang@chromium.org
, Oct 9