I regularly see feature requests on Meta, sometimes with heavily upvoted answers. A feature request is not really a question with an answer since the poster is asking for a feature to be added to the site.

  • How would I write a good answer to a feature request?
  • How could I write an answer to my own feature request?
  • What should I include?
  • How simple or complex should my answer be?
  • Also, could I write an answer to my own feature request?
  • 4
    One option is the No, we do not want this answer. – rene Dec 5 '18 at 16:15
  • @rene only when it comes with explanation and too long to fit as comment. :) – Shadow Wizard is Ear For You Dec 5 '18 at 16:27
  • 1
    Stop making trivial edits. It doesn't help do anything, and just annoys readers. – fbueckert Feb 14 '19 at 0:51
  • I am stopping that – Asadefa Feb 14 '19 at 0:51
  • 1
    @fbueckert those are not trivial edits. OP is trying to add back the wrong meta tag. (Added by mistake by a new user who likely had no idea it's only for questions specific to MSE, it should not have been approved) – Shadow Wizard is Ear For You Feb 14 '19 at 7:55
  • Doesn't it also apply for the meta as well as per site meta? – Asadefa Feb 15 '19 at 4:24
  • 1
    With reagrd to your latest edit, I think the "answering a bug" part should be a separate question – Jenayah Feb 17 '19 at 19:39
  • @Jenayah ok, how about I ask that as a question – Asadefa Feb 17 '19 at 19:40
  • Yeah, that's what I meant :) not sure whether it'd be a dupe or not, though – Jenayah Feb 17 '19 at 19:40
  • @Jenayah if it is close enough, it should be added on to this question. Is answering a bug similar enough? – Asadefa Feb 17 '19 at 19:42
  • Dunno, never really answered a bug. Maybe @ShadowWizard can say, as they already answered here – Jenayah Feb 17 '19 at 19:44
  • @Jenayah ok then – Asadefa Feb 17 '19 at 19:45

As ordinary user, answering a feature request can be done in such cases, in my opinion:

  1. Suggesting a "tweak" in the request, which still preserve the original idea but with something a bit different. This is useful to prevent many duplicate requests being posted as different questions. Recent example. (Yes, by me. :))
  2. Suggesting a technical way to implement the request. This can help the team in case they decide to do that is being requested, ans save them some time. Example where it was being done. (not recent)
  3. Suggesting a workaround/alternative way to achieve the goal of the request, using things that already exist. This is useful since it achieve the goal, without waiting for SE team to do it. Example. (By me. :))
|improve this answer|||||
  • Could you also explain why or why not you agree? – Asadefa Dec 5 '18 at 16:29
  • 4
    @myasadefa why you agree rarely justifies answer, just upvote, maybe comment, and when having the rep, start a bounty. Not agreeing sometimes can be done as answer, yes, as rene mentioned in comment and linked to proper example. – Shadow Wizard is Ear For You Dec 5 '18 at 16:30
  • How also can I answer a bug? – Asadefa Mar 21 '19 at 4:01
  • @Asadefa two main ways for bug reports: 1) Suggest a way to fix it, in a simple and doable way, to save time for SE developers, or 2) Explain why you think it's not a bug, i.e it should be declined or marked as status-bydesign. – Shadow Wizard is Ear For You Mar 24 '19 at 9:12
  • @awizardarachnid maybe, but the user asked in a comment. – Shadow Wizard is Ear For You Mar 24 '19 at 16:27

You must log in to answer this question.

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