Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

The red tags/moderator tags/status tags — except for [status-review], perhaps — on Meta indicate that a mod has considered a feature request or bug and made a decision about how to handle it. In other words, they tend to equal "this is the official answer from the admins."

Over a hundred questions in the Unanswered list are marked [status-completed] right now, mostly quick bug reports that don't require long explanatory answers. Depending on how you look at it, they'll never be answered, they can't be answered and/or they've effectively already been answered. Could questions with red tags be filtered out of the Unanswered list entirely?

share|improve this question
+1 This sounds like a great idea. – Fosco Sep 23 '10 at 19:52
-1 The text on your avatar is too small. – Tyler Carter Sep 23 '10 at 19:56
0 I like no-ops. – JSONBog Sep 23 '10 at 20:03
what about [status-declined] requests that actually most users want? And sometimes even happen to be changed into [status-completed] at a later point? – Tobias Kienzler Sep 24 '10 at 8:23
@Tobias, they'll still show up if you search for the tags. I guess this comes down to how people use the Unanswered tab. I do it when looking for things that haven't been addressed at all, and regardless of what might happen in the future, anything tagged [status-declined] has technically been addressed. – Pops Sep 24 '10 at 14:42

This is still a problem.

Fortunately, it seems to have gone down in the past year. However, it hasn't been eliminated.

For some questions, such as tag merge requests, a simple, one line answer "It has been done" is sufficient. For example, see this question. There is resistance to the need for answering instead of just retagging.

Answers to questions should have a description of the feature in the answers. For an example of what to do, see this post or this one. For an example of what not to do, see this post which was marked as , which failed to notify the OP, leaving the OP to speculate that it had been done when the effects were observed sometime later. The OP had no reference to implementation discussion elsewhere, a post which was not marked .

posts should contain reasoning as to why the feature was not implemented. Important content like this does not belong in the comments.

share|improve this answer
Update: Now 95 unanswered, 16 declined, 11 norepro. It's going up! – Kevin Vermeer Apr 13 '12 at 1:20

Well, yes there are 105 unanswered marked [status-completed], but that's out of over 1,100 questions total, so I don't see this as a problem, nor do I think it needs special SE programmer team attention.

If you want, go ahead and resurrect this question. I'd support closing the ones that are legitimately completed and/or no longer relevant.

share|improve this answer

You must log in to answer this question.

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