I'm in favour of closing tickets with "need more info, re-open when you have it or if you disagree" because it clearly puts the onus back on the reporter to re-open the ticket after addressing the feedback in order to see any progress.
Leaving tickets "open" with potentially yet another status or flag indicating that it needs some type of action will just contribute to the problem we already have with many tickets stagnating in some combination of "open" for literally years without any action. If a ticket is marked as "needs more info" while remaining open, it may be that only the original reporter (or somebody who is seriously motivated to dig) will be able to provide that more info, and if it's off their radar for whatever reason the ticket will likely remain in that state forevermore. Cheers. Tai. On Nov 17, 1:01 am, Andrew Godwin <and...@aeracode.org> wrote: > It was ticket state, not closing state (sorry about the reply lag!). I > guess it's more that I don't like closing bugs purely because they've > not got enough information - it gives the wrong impression in my mind (I > only close once I have positive affirmation that it is invalid, > worksforme, etc.) > > This is, I suspect, more a relic of the way I use Trac. I'm fine with a > closing state as well, I just feel like closing tickets before we even > know what they are sends the wrong impression. > > On the other hand, we want to keep the trac as cruft-free as possible, > so I suppose closing tickets is fine in that regard. The ticket state > proposal has merit in that it can be crafted so that someone replying to > a ticket in needsinfo state moves it back into a "normal" state, thus > needing the minimum level of Trac competency from the reporter, and not > presenting a rather imposing "ticket closed!!!" interface - getting to a > project's ticket and finding it closed deters me from replying a lot > more than finding it in a "needsinfo" state. > > Andrew -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
