Currently there are 57 questions tagged as feature request + status-bydesign (75 minus 14 where there is also tag minus 4 that also have ).

Without looking into each of those I just think that logically speaking, feature request can't really be by design. It can be either rejected or accepted (completed).

What should be done about this? In my opinion most of those should be changed to status-completed or status-rejected instead of "bydesign" or other possible way to make it correct is changing the feature-request tag to "support" or "discussion".

  • 2
    I think you already know this, but [feature-request] [by-design] means "The system already works the way it's intended to work, without the additional functionality your feature request would provide."
    – user102937
    Dec 31 '12 at 20:35
  • 1
    Should be [status-declined] if the feature request is declined for whatever reason, including that of the feature being absent by design.
    – user200500
    Dec 31 '12 at 20:40
  • 2
    @RobertHarvey Or occasionally "with", when the functionality already exists. :)
    – Adam Lear StaffMod
    Dec 31 '12 at 20:42

Yeah, this arrangement does seem a bit incongruous... A spot-check seems to indicate that most of these should be retagged in some way: either by changing the status to declined/completed, or by changing to or .

That said... Meh.

  • 2
    Yeah, I reluctantly throw "bydesign" on feature requests when the post obviously is a feature request for something that just happens to already exist. I suppose I could edit to make it a support question instead, but... meh.
    – Adam Lear StaffMod
    Dec 31 '12 at 20:42
  • Retag to status-completed to improve your KPI up the bronxzoo
    – random
    Dec 31 '12 at 21:08

You must log in to answer this question.

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