Questions and bug-reports seem to get deleted without notice here on meta.

I posted a bug report about 20 minutes ago, which just disappeared. This question

was posted as a follow up (which politely asked why), and was also deleted without notice.

My question:

Is this behavior documented / motivated somewhere?

(I'm fine with it if there is some official motivation saying that "noise is removed" to keep the sites clean, provided there is an objective understandable definition of noise.)

(PS. My original question was restored and answered. -- Thanks Jeff, I appreciate it. :)

(PPS. But is now removed again. I guess because it sort of clutters the forum.)


If the bug is related to a build artifact that will exist for all of 5 minutes, after which point it will automatically correct itself -- this "bug" is of no future value and does not need to exist at all.

Basically, "wait 5 minutes, and you'll never see this again for the entire history of recorded time."

Sort of like "too localized", but of even less value...

edit: Fine, though I think it's pointless to dwell on a 15 minute issue, here's the master: https://meta.stackexchange.com/questions/105882/what-happened-to-the-author-info-avatar

| |
  • 12
    Why didn't you leave one report with an answer/comment stating this for the duration and then delete that. – ChrisF Sep 12 '11 at 8:11
  • 6
    Aha, I can understand that. But can't you close the question with some close-message or something? It's extremely frustrating to see pages you're reading / discussing on just vanish. – aioobe Sep 12 '11 at 8:12
  • 13
    In this particular case it's worth noting that there were at least (by my count without access to deleted questions) 3 bug reports for this, probably more. Wouldn't it be easier just to respond to the first bug report, say "this is a problem with the latest build and will be fixed in 5 minutes", fix the problem, and then deal with any duplicate bug reports after the problem is fixed, instead of wasting time deleting every repeat bug report (because multiple users think, "odd, there's no bug reports for this yet!") and confusing the users? – nhinkle Sep 12 '11 at 8:12
  • @nhinkle I like rewriting history, actually, and this build situation should never have existed. Now it doesn't. Also you're talking about a fifteen minute interval here.. – Jeff Atwood Sep 12 '11 at 8:13
  • 6
    Ah yes. We've always been at war with Eastasia, and the builds have always been flawless. Understood :D – nhinkle Sep 12 '11 at 8:16
  • 8
    @Jeff: What you are doing extremely irritates users. Your last comment just shows how much you respect your users. You don't like that there was a bug in your software so you delete every occurrence of a bug report? Seriously? As others have mentioned, just answer one and link all others to that one. After the bug is fixed and some time has passed, you can still delete those bug reports, because THEN they are of no more value. – Daniel Hilgarth Sep 12 '11 at 8:19
  • 6
    I totally agree that it's completely okay to delete bug reports, but why not leave one alive, put a "It has been fixed now, thanks" answer underneath, wait 12 hours, delete with no one ever noticing. Just to prevent this kind of discussion every time – Pekka Sep 12 '11 at 8:22
  • 1
    Idea for a new field on a bug tracker: Should this bug ever have existed: Yes / No – AakashM Sep 12 '11 at 8:33
  • 1
    @Jeff: Although you undeleted the question, your comment shows, that you don't seem to understand the real issue here. When you delete those bug reports without any feedback, the users can't know whether it is a bug that will be fixed in no time or a new feature you would like to suppress discussion about. Clarifying that it is just a bug and will be fixed will prevent all this uproar and will cost you less time than all the deleting and discussion afterwards... Don't you think so, too? – Daniel Hilgarth Sep 12 '11 at 8:44
  • 1
    Cool! I like the new policy. Time rewrite 90% complete. Tomorrow, this is how we will remember the past 60 minutes: bit.ly/oPA4xG – Pekka Sep 12 '11 at 8:54
  • 3
    @Jeff: Well, yes. Features were introduced in the past that created a big uproar in the community - the removal of the envelope for example. Questions, answers and comments where massively deleted back then. A lot of people thought the new implementation didn't make sense and saw the removal of the envelope as a bug. So, just because I think a change doesn't make sense, doesn't mean it is a bug - it could be a new feature. After the questions about this particular bug got deleted, I actually began fearing that this was a new feature, because I could think about some arguments supporting it. – Daniel Hilgarth Sep 12 '11 at 8:55
  • 3
    @Daniel come on, it was a five minute bug. I'm in favour of putting this to rest now. The first bug report has been undeleted. What more could one want? – Pekka Sep 12 '11 at 9:00
  • 1
    @Pekka: I think it is important that Jeff understands our side of this discussion. It has nothing to do with that particular question but with the general behavior of the mod team on meta. Basically, I hate coming here because of the way people are treated. I would like this to change. – Daniel Hilgarth Sep 12 '11 at 9:04
  • 1
    @aioobe: How do you know? It doesn't look like this to me. Or he does and doesn't care - which would be even worse. – Daniel Hilgarth Sep 12 '11 at 9:11
  • 2
    Folks, this horse has been beaten to death. The fact that Jeff decided to restore the first report and slap a [featured] tag on it shows that he does, in fact understand the arguments here. The requested action was taken, the bug is fixed, I don't see the need for any additional discussion. </thread> – Tim Post Sep 12 '11 at 9:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .