| Bug #36501 | Bug reports 'time out' and are closed | ||
|---|---|---|---|
| Submitted: | 5 May 2008 9:51 | Modified: | 24 Jan 2014 11:01 |
| Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Websites: bugs.mysql.com | Severity: | S4 (Feature request) |
| Version: | hmmmm ... | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[5 May 2008 9:51]
Peter Laursen
[5 May 2008 10:34]
Tonci Grgin
Hi Peter and thanks for your reasonable feature request: "Make any post to bug report revert it to Open state" I don't see this as BugsDB fault but rather a fault in Bugs team procedures as there is always a possibility that original reporter forgets to change the status of problem. Anyway, I'll let Jim decide. --<cut>-- 1) some user posts a report 2) some MySQL person asks more questions and changes status to 'need feedback' 3) some *other user* provides the requested information 4) status will NOT change from 'need feedback' to 'open' 5) the *original reporter* does nothing as he thinks that requested information have been provided. 6) also it seems that the MySQL person assigned with this report is not notified 7) after a month the report will be closed by the system due to lack of activity unless the *original reporter* understands that *only he* can change the status and notify the MySQL person! --<cut>-- Point 5) is doubtful as there is *no* definition of "enough info". Even when MySQL staff is off-topic, reporter *should* provide requested info. This is, in my opinion, non-negotiable as primary purpose of BugsDB is to generate additional value to community, and any member can find himself/herself satisfied with additional info provided. There is also a matter of complexity. How am I supposed to distinguish between several reports if only basics are provided? Am I to neglect several serious reports and go writing test case from the scratch even though purpose / problem is not clear to me? Reporter neglecting it's own bug report is simply rude to entire community... As for point 6), I always subscribe to any of reports assigned to me (and to some of interest) so there is no chance for me to miss any post. It also happens that, due to explanation given in description for point 5), I use my right to neglect some report. It basically happens with reports satisfying all of following conditions in exact order: 1) Reporter has made poor case explaining 2) There is no added-value in report for community (test case or such) 3) Reporter has neglected all of my requests 4) Problem can be solved by looking into BugsDB / manual 5) I, personally, find the problem described in report of less importance / impact ... As you can see, my personal opinion comes last and only after report is declared as a really bad one. Even in such cases I often test myself, but this slows work down significantly leaving other reporters waiting long for response. Point 7). If any of MySQL staff is subscribed to report, he/she will get e-mail from anyone posting. As for above mentioned report, you are completely wrong. Let's take a peek in it: - Valeriy tried several times to reproduce it and failed. Instead of marking it CRp and forgetting, he pings me to continue investigation. - I remembered a thread describing similar behavior, left you a response and now I'm waiting for more team members to come on line. So I think Bug#36491 proves the contrary! Not only that it was picked up in a day, but in two days time you got two support engineers working on it. Finally, be aware that Bugs team is 5 persons only. We have to get people generate added value for MySQL & community and to help us follow through! I think that's small request for service we provide for free.
