I'm sure this has been suggested before...

I'm doing my part to reduce the issue queue backlog. I'm wondering why we don't automatically:
1) Add a comment looking for follow-up info for issues over a year old and changing status to "Needs information"
2) Closing the issue after another three months of no activity

Just wondered...

Comments

dddave’s picture

dddave commented

I am also working on reducing the gigantous backlog of D6 core issues because I feel that large issue counts don't make a good impression on newbies. Some way to automatically reduce old issues would be nice. Perhaps we can exclude bug reports is such a behavior is incorporated.

gagarine’s picture

gagarine commented

I don't think we should ever close an issue if it not solved. But I do agre than so much open issue is bad.

What about a "inactive" statu? Issue with no activity after x time change to "inactive". Inactive issue of unsupported drupal version can be close...

dpearcefl’s picture

dpearcefl commented

An issue that is very old is likely to have already been solved. If you first mark the ticket as "needs information" and if there is no followup by anyone in several weeks, then the ticket should be considered abandoned and closed. Otherwise it is just noise in the queue that makes Drupal look bad.

igorik’s picture

igorik commented

this can help with this issue, comment closer module
http://drupal.org/project/commentcloser

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented

[ Powered by #1115636: Issue Macros and Templates - _default]

This is similar to #1273746: Automatically close old project-issue nodes with category 'Support'

This is similar to #1377678: Automatically close support issues after X days

barraponto’s picture

barraponto
he / him
commented

If an issue gets into "postponed (mantainer needs more info)" and there has been 6 weeks since last comment, we should change its status to "closed (cannot reproduce)".

We shouldn't check time since status was set to postponed because we cannot assume requesters are status-savvy and will change it back to active. So checking since last comment is a better method to predict.

We might have to put into account the project "Maintenance status", even if they lie.

xjm’s picture

xjm
she/her
Primary language English
commented
Status: Active » Closed (duplicate)

Fairly a duplicate of #156704: Dealing with "postponed (maintainer needs more info)" issues.