Could the bug category be excluded from auto-close, or the time be extended?
There was already similar thread about it (Forum settings for topics - #4 by ByteHamster) and there were some changes and motivation was given by @ByteHamster and supposedly Bug report category was excluded yet my bug-report was closed after 120 days:
Now there may be a justification for auto-closing even bug-report category (obsolete issues) but IMHO having longer period (maybe a year?) and maybe a pre-close notification that the thread would be closed could be added?
Why I’m mentioning it? The aforementioned issue with playback notification being gone still happens, I’m on 3.8.0f and that issue is basically driving me nuts as to stop the playback I have to unlock the phone and then open the app instead of quickly stop the playback from the notification
That problem is known and annoys me as well, but so far nobody found a proper fix. It definitely won’t be forgotten even if the thread is closed We also have an open issue over on GitHub for this.
The problem with longer timeouts is that users keep hijacking old threads to post their unrelated issues
In that vein, I appreciate how @keunes closed a new (but actually redundant) feature request yesterday and moved the contents to the existing feature request.
The problem with moderation is that someone needs to do it. Also, by the time a user posts to a wrong thread, the others receive an email notification about the unrelated issue. Automatically locking the threads prevents that
I don’t think increasing that number every time this comes up (I think we already increased it twice) will really help. There probably is no perfect solution as long as people don’t start reading before they post
Which is why I suggested instead to tag @moderators so we follow up when needed (without having to continue increasing the period bug reports stay open)
We also have an open issue over on GitHub for this.
