Currently we have 1356 bug reports that are not closed, have zero answers and no [status-*] tag.

Why aren't we getting feedback from the DEV team about these reports? Has the team even noticed every single bug report? I fear not since not even all bounty questions get noticed by the team certainly.

Even if the bug won't get fixed it would be nice to get a quick response to know what the team thinks about that.

  • 1
    I think Anna response to this recent question on same topic sums it up nicely: We try, but we could certainly do better Commented Jul 1, 2013 at 12:19
  • 3
    Just to note: Currently we have 145 bug reports that are not closed, have zero answers and have status tag.
    – Himanshu
    Commented Jul 1, 2013 at 12:19
  • Shouldn't we be looking at that number in proportion to the total 9,310 [bug] posts? Also, I don't know if we should count the ones that have no upvotes, or that do have an applicable status tag. meta.stackoverflow.com/… Commented Jul 1, 2013 at 12:21
  • 1
    @BilltheLizard: And there are certainly also bug reports with (unhelpful) answers but not from the dev team. Even if the essence are only 1000 unanswered bugs or less - it could still be much better.
    – juergen d
    Commented Jul 1, 2013 at 12:38
  • 2
    To pick just one example, this bug ( meta.stackexchange.com/q/181929/147655 ) has one answer from me which helped in clarifying the problem, but did not solve it at all. It should be considered [status-pending], but there is no such status tag. Commented Jul 1, 2013 at 12:48
  • 1
    @DanielDaranas There are [status-planned] and [status-deferred]
    – Bart
    Commented Jul 1, 2013 at 12:49
  • 2
    Note that many of the devs seem to be working on Big Things, and don't spend much time on Meta. (also I think they have a rotation of Meta duty, but that's a guess). As such we don't have that many devs available for [status-complete]ing duty. Commented Jul 1, 2013 at 13:12
  • 1
    @Manishearth: Personally I would like to think DEVs spend a little time here every day to get what is going on on their network.
    – juergen d
    Commented Jul 1, 2013 at 13:30
  • 3
    Why not see how many devs you can pick out here, @juergend? I count 5 on just the first page...
    – Shog9
    Commented Jul 1, 2013 at 14:18
  • @Shog9: I was just refering to Manishearth statement that DEVs probably don't spend much time on Meta. It's really great that this is not the case like it seems.
    – juergen d
    Commented Jul 1, 2013 at 14:22
  • 3
    Now see what you've done! ;) Commented Jul 3, 2013 at 8:02

2 Answers 2


We could do better than we do. It's not just the development team that should be patrolling for these, it's also the community team. It's going to take some time to go through the list, but I'm going to venture that it's not quite as long as it seems:

  • The 'bug' tag is applied incorrectly when reporting intended behavior from time to time
  • Some of these were likely duplicate reports that just went unnoticed, and have been subsequently fixed with a reply posted elsewhere

Keep in mind that we have well over 100 child meta sites, which the developers also patrol along with us. We can't always count on bugs that aren't specific just to certain sites (like a styling glitch) to be migrated here to Meta SO.

This is also a bit of an issue when it comes to feature requests - something we've addressed by bringing quite a few open feature requests into a weekly meeting where we discuss them and pass some on to the developers with our notes and changes. We are trying to get more efficient overall.

We do our best to make ourselves as accessible as possible to the community. While yes, we do sort of stink sometimes at catching things that need our reply - a lot of other services at our scale have perfected the art of making themselves very difficult to reach. We don't want to be 'that guy'. We'd rather lag a bit than become more insular.

That said, if you notice something you reported not getting any attention (and you're certain it's not actively being discussed on another bug report) you can do the following things:

  • Send the community team an email, show us the meta post and let us know it's still broken and driving you nuts
  • Ping one of us in chat (generally the fastest way, but pings sometimes get lost)

If you haven't noticed, we're also hiring like crazy! As new people come on board and begin filling the roles which have been gaps in our teams, our bandwidth and responsiveness will naturally increase. Part of the problem is simply not having enough hours in the day. I'm sure you've heard jokes about the management here being slave drivers, but they actually kind of insist that we go home and not work for a while every day if you can believe that.

Improvement should be coming in the near future, and thanks for the prod.

  • 3
    Two and half years later, have there been any improvements? :) Commented Dec 27, 2015 at 15:35
  • @ShadowWizard, so this explains it. I have two posts here, both bug reports, both no response. Why Bother? Commented Oct 20, 2017 at 6:03
  • @StephenRauch because some bugs are fixed. Some faster than others. So we have hope. It's not perfect, but it's working for years, and isn't really bad. Better than all other sites I know of, which don't have any such system to begin with. :) Commented Oct 20, 2017 at 6:04
  • @ShadowWizard, yea, but we don't invest nearly at much in those others sites. Do we? Some acknowledgement would be nice. I won't be back to meta... Commented Oct 20, 2017 at 6:07
  • @Stephen you really take it way too far. I mean, that's your choice, but if you'll just understand the process you'll feel much better. If you want to try, hit me up on chat. Commented Oct 20, 2017 at 6:09
  • @ShadowWizard, do I have enough rep for that here, or should we take this somewhere else? Commented Oct 20, 2017 at 6:11
  • @StephenRauch yes you need only 20 rep to chat. chat.meta.stackexchange.com/rooms/721/shadows-den Commented Oct 20, 2017 at 6:18

I think the only sane way to look at this is:

Basically, this query. That's 1,104 results. The first 50 descend to score of 15. The second 50 descend to score of 12.

I think it's fair to ask the team to post some kind of response to any so-called "bug" with 20 or more question votes as a general policy. That's around 25 items based on the current list.

  • 6
    As a note: "Real" bugs sometimes don't get much attention and upvotes. It often depends on the time posted. So upvotes aren't an exact measure to get real/important bugs.
    – juergen d
    Commented Jul 6, 2013 at 10:44
  • 1
    @juergend Well, if you consider that making a couple of passes similar how how Jeff suggests would put a big dent in it, then the bugs that managed to go without much notice become much easier to find. You just keep slicing off the top of the stack, which is what they're doing.
    – user50049
    Commented Jul 17, 2013 at 12:26

You must log in to answer this question.

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