New issue
Advanced search Search tips

Issue 613153 link

Starred by 3 users
Status: WontFix
Owner:
cda...@chromium.org
Closed: Aug 2016
Cc:
gov...@chromium.org
lafo...@chromium.org
mbarbe...@chromium.org
cda...@chromium.org
infe...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Sheriffbot-Auto-triage Rule: Archive Available bugs which have no categories and not modified for an year

Reported by mexmat.s...@gmail.com, May 19 2016 
Sheriffbot-Auto-triage Rule: Archive Available bugs which have no categories and not modified for an year.


Add Bug number which got updated: 489839


Issue/Concern or feedback: While the bug was not been appropriately triaged by the Chromium team (despite label NeedsFurtherTriage) it's still trivially reproducible.


Any other important details: This is a documentation bug/omission, not a bug in Chrome code.

Comment 1 by mexmat.s...@gmail.com, May 19 2016 

Additional notes:

1. Not having the EditIssue privileges, I cannot reopen the original bug as suggested by sheriffbot.

2. I am submitting this issue because this is a remedy mentioned on https://www.chromium.org/issue-tracking/autotriage

3. Labels requiring more triage should probably trigger a different action than archiving (e.g. recharge)

Comment 2 by lafo...@chromium.org, May 28 2016 

We might want to consider making it so that if the a comment is registered after we auto-archive of an issue, we automatically re-open it, for some period of time (e.g. up to 30 days).

Comment 3 by lafo...@chromium.org, May 29 2016

Labels: Hotlist-SheriffBot

Comment 4 by mbarbe...@chromium.org, Jul 22 2016

Components: Tools>Stability>SheriffBot

Comment 5 by cda...@chromium.org, Aug 1 2016

Cc: -cda...@chromium.org gov...@chromium.org
Owner: cda...@chromium.org

Comment 6 by cda...@chromium.org, Aug 31 2016

Cc: mbarbe...@chromium.org
Status: WontFix (was: Assigned)
We discussed this in our meetings and decided we won't re-open the bugs automatically as it may lead to false positives in many cases.

Since the bugs which are in concern are not modified for an year, it is unlikely to receive any attention, so best way is to report a new bug to get prompt response.

We already add this the comment "Please re-open or file a new bug if this is still an issue".

Thanks
►

Sign in to add a comment