0

After surviving nearly a month in the meta, I understand that feature requests are reviewed and given a status (any status after review - accepted, declined, by-design, under-cons...) based on the number of upvotes.

My Question:

  1. If a feature request is repeated as a duplicate, will the votes in duplicate count too? Will the votes cumulate?

    • Many feature-requests have duplicate status and the votes on the original post varies widely from the votes on the duplicate post (may be more or less)
  2. Do the number of duplicates also count toward being given a status?

To summarize, if a feature request is duplicated n times, will the 'n' also count along with the upvotes?

Edit:

The most important thing you can do to help support old feature requests is upvote them. The reqs tab is around to basically mirror the process that the team uses in deciding what might be important to look at. They are more likely to spend time looking into a feature that has some level of community support. This has been repeatedly stressed by the Team at various points.

Really, this is sometimes more useful than paying heed to the status tags. Even officially declined requests may end up implemented after reconsideration. The important thing is to give good reason for reconsideration - bump it with an answer that provides additional data in addition to upvoting it. If you can bring enough support to the idea, it increases the chances that it will get looked at.

This was taken from answer here given by Grace Note.

Edit 2:

Let me make it crystal clear, I am not asking about implementation of a requested feature, just review of the feature by the official team and giving a status to the request. By status I mean the request has been seen by the official team and considered as an option and debated upon. Then finally the conclusion of that discussion is posted as status. (Or whatever process a request undergoes)

3
  • 2
    "based on the number of upvotes" ... nope. They are just evaluated as is. Popularity might help push an idea forwards, but that's not really a consistent deciding factor. And duplicates are just ... duplicates. There isn't really a whole lot of influence there, nor any concrete mechanism.
    – Bart
    Jan 29 '15 at 12:43
  • @Bart the post quoted seem to disagrees opinion about votes, though I understand what you mean
    – One Face
    Jan 29 '15 at 12:48
  • I remember reading from Jeff Atwood, the same thing somewhere, though I can't find it now
    – One Face
    Jan 29 '15 at 12:49
8

Based on what I've seen, I'm quite certain that the score of a feature request is only one factor considered --- and not the most important factor --- before declining or accepting a feature request. Some heavily upvoted feature requests have been declined. For instance, see this one, which stands at a score 618 as we speak, and yet was declined.

I doubt there is any kind of vote summing from across duplicates, or that the multiplicity of duplicates is a factor in favor of a feature request being implemented, but someone who's actually in the know would have to confirm.

Regarding Grace Note's quote, she says:

The most important thing you can do to help support old feature requests is upvote them.

I disagree with this. It is the easiest thing one can do to support a feature request but not the most important. Again, this is based on how I've seen feature requests being handled. In my opinion, the most important thing is (still quoting Grace Note from the same quote in the question here):

The important thing is to give good reason for reconsideration - bump it with an answer that provides additional data in addition to upvoting it. If you can bring enough support to the idea, it increases the chances that it will get looked at.

This is the most important thing. Giving a good rationale is much more important than a vote.

6
  • Thanks for the quick reply - I knew that upvotes are not the criteria for acceptance. That's why I specifically asked for status update or review of the feature request
    – One Face
    Jan 29 '15 at 12:34
  • From your question: "I understand that feature-requests are reviewed or given a status based on the number of upvotes." I understand this to mean that the status that is given is based on the number of upvotes, which for me translates to "high score == status-accepted", "low sore == status-declined". If you meant something different, then you'll have to write your question differently.
    – Louis
    Jan 29 '15 at 12:36
  • I meant just status - accepted, declined, by-design are all statuses. Nevertheless I will edit the question to be more clear
    – One Face
    Jan 29 '15 at 12:38
  • Is it clear now?
    – One Face
    Jan 29 '15 at 12:41
  • And as a counter example: -22 and status-completed meta.stackexchange.com/questions/131029/…
    – Bart
    Jan 29 '15 at 12:45
  • I think I have made the question clearer now. I am not concerned about implementation of any feature, just the process of the post being evaluated as a request by the official Dev team. I think that is what Grace meant when she posted that
    – One Face
    Jan 29 '15 at 13:12

You must log in to answer this question.

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