6

On UserVoice, it's clear how the bug/feature request procedure works:

  1. Enter a bug
  2. Gain votes (or don't)
  3. Get declined by an admin or get a bug fix

How will this work on Meta (this site? Is there any suggestion for this? I would like to see the status of my requests.

  1. How should I tag feature requests?
  2. How should I tag bug reports?
  3. In what way are bugs handled?
  4. In what way are feature requests handled?
Improve this question
3
  • If your question is closed, it's done :}
    – Ladybug Killer
    Commented Jun 30, 2009 at 7:44
  • Jeah, but I don't know what's happening :)
    – please delete me
    Commented Jun 30, 2009 at 7:45
  • Related, from an FAQ entry: list of special tags on Meta agreed upon after this question was asked (and likely in part because this question was asked)
    – Pops
    Commented Oct 11, 2012 at 18:10

2 Answers 2

Reset to default
7

Here are my thoughts

  • Make sure the item is tagged [bug] or [feature-request].
  • Moderators will review all questions with those tags periodically
  • Moderators will apply moderator-only tags to the item to indicate its status

What are some moderator only tags we might need? Ideas:

  • [status-completed]
  • [status-norepro]
  • [status-declined]
  • [status-accepted]
  • [status-deferred]

?

The only time to close is when the item is truly done and complete, forever. I suspect we will use the tags more often for that in case there is further discussion necessary of our "fixes" which sometimes are not so.. "fixed".. or have other related issues, etc.

Improve this answer
7
  • 1
    The user tags are perfect, I would do this. The moderator tags should be documented in any way, probably in faq? I'll post my question as CW, so this could be the collection for moderator and user tags.
    – please delete me
    Commented Jun 30, 2009 at 7:48
  • 1
    Your list of tags is a good start. I would stick with them for the beginning. Start simple, more will be added when they are needed. Ok, I stop telling you the obvious procedure ;-)
    – Ladybug Killer
    Commented Jun 30, 2009 at 7:56
  • I tagged it as "meta-faq" and CW so that it can be discussion and faq at the same time.
    – please delete me
    Commented Jun 30, 2009 at 8:01
  • 3
    You should make sure that users can't create tags that start with [status-].
    – Brad Gilbert
    Commented Jun 30, 2009 at 13:40
  • Although tagging as 'feature-request' or 'bug' will certainly work, I'm sort of hoping for an out-of-band method for handling the status similar to closing. However, as long as they're distinguished in some way (different color?) this could work.
    – Kyle Cronin Mod
    Commented Jul 1, 2009 at 17:50
  • what exactly does [status-norepro] mean?
    – aug
    Commented Aug 21, 2013 at 17:58
  • 1
    @aug status-norepro means that the bug can't be reproduced by Stack Exchange developers, hence can't be fixed.
    – Shadow Wizard
    Commented Jun 27, 2022 at 14:26
4

While moderator specific tags are a good idea, would new MetaSO-specific close reasons work better than (or at least in concert with) tagging? Closing as "No longer relevant" is a little vague, but closing as "New feature declined" or "Bug fix completed" is more informative.

Improve this answer