I don't know if this is the correct section, but I'd like to share my 2 cents on bug report threads.
Sometimes I found that topics are moved into "not a bug" section without a single word explaining the reason. Sometimes it is quite clear, because there's a discussion in topic, but some other times they are simply moved there.
Considering that I suppose devs give a look at "not a bug" section not very often (if any), it can be really bad for a topic that IS a real bug but maybe has been wrongly explained etc. I also found it is not easy to let these thread came back to devs attention.
A similar case happens when a bug is in "Resolved for the next release" or "Resolved Problems and Bugs" sections: I think there almost no possibility to be watched by devs again: on other forums I found that closed bugs' thread are locked, to prevent "unuseful" discussions going on there (I mean "unuseful" because there are not watched by devs).
What are your opinions about these points?
[Forum] Some ideas about bug reports threads
Re: [Forum] Some ideas about bug reports threads
I don't know about the other devs, but I watch all the subforums of bug reports.... but it's better to open a new thread if the bug is marked as resolved and in fact it isn't.
Re: [Forum] Some ideas about bug reports threads
oh, I'm happy about that. Thanks!cube wrote:I don't know about the other devs, but I watch all the subforums of bug reports
what do you suggest in case of thread marked as "not a bug" but I'm sure it is? like this thread that according to me should be in "minor issues" instead of "not a bug"?cube wrote:it's better to open a new thread if the bug is marked as resolved and in fact it isn't
Do you suggest to open a new one or writing reasons why for me is a bug in-topic is enough?
Re: [Forum] Some ideas about bug reports threads
Yeah, when we explicitely move it to not a bug, it's probably best to just try and write up your arguments for whay it is a bug.... (and in this case i also think it isn't, see the post in that thread).