There are over two thousand questions on Meta Stack Exchange tagged that have no answers (and haven't been closed). This doesn’t include all unresolved bugs, just the ones that haven’t had any answers at all.

[bug] answers:0 closed:0; 2,251 results

Some of these look like they may have been resolved by changes that have been made since they were posted (such as by the recent changes to reputation), but are still here as noise, burying other issues that are potentially more serious (such as those that prevent a user from participating fully, or from logging in at all).

It’s obvious that this tag needs to be cleaned up. Issues that have been addressed don’t indicate that, and issues that haven’t been addressed are buried under all the noise.

Is there anyone at Stack Exchange whose job it is to monitor bug reports, or will it be up to the community to go through and answer all these questions (though most of us can do nothing about the status tags)?

  • 17
    – user102937
    May 29, 2012 at 16:22
  • 2
    lyk dis if u "so what" evrytim .. 5eva
    – jcolebrand
    May 29, 2012 at 16:24
  • 2
    @RobertHarvey not STATUS=BYDESIGN? Let's at least claim it's a feature, not a bug.
    – Bart
    May 29, 2012 at 16:40
  • 7
    Let's fill the meta flag queue to the size of the SO main flag queue! Mission acquired, commence operation...
    – animuson StaffMod
    May 29, 2012 at 17:41
  • 5
    @RobertHarvey I don't that would work (based on the Data.SE) it would be UPDATE posts SET Tags = Tags + ' status-declined' WHERE id IN (SELECT id FROM Posts q WHERE answerCount = 0 AND PostTypeId = 1 AND tags LIKE '%bug%' AND tags NOT LIKE '%status%' AND Datediff(y, creationDate, Getdate()) >= 1) May 29, 2012 at 18:21
  • 6
    @SomeHelpfulCommenter: I knew someone would come along and declare my pseudo-SQL invalid. :P
    – user102937
    May 29, 2012 at 18:43
  • 1
    @RobertHarvey wait... you actually expected a meta.SO user to come a long and suck all the fun out of a comment by responding with a technical clarification. You're pretty jaded. ;) May 29, 2012 at 22:33

2 Answers 2


We need a rather organized way to do this. I went through a whole bunch of posts, and answered some. But it's a big task and we need to work together here.

Here are some points I've sketched out:

1) If the question has been fixed, answer (with evidence), and flag for

2) If there is a dupe, give it a close vote and try to get more CVs. We can add a CW post below this where we list stuff that needs CVs (and whoever casts the fifth/binding CV must remove it from the list). Chat also works, but it may become unwieldy.


Please do not vote blindly, go through the post first.

If you cast the 5th/binding vote, please remove it from here.

Bugs needing close votes

Upvotes above your rep cap disappear from your Reputation view


You must log in to answer this question.

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