This isn't covered by How does Meta Stack Exchange work?, as that just explains the tags, but I want to know how they are used by the staff. From experience this differs from the tag description.

As an example, see this answer:

Marking this as since we are not going to be able to get to it in the near term due to the difficulty of fixing issues like this in chat (and it's accompanying Elastic service that is used for search indexing). It will stay in our books as an issue to fix if/when we are able to prioritize chat issues like this again.

(Emphasis mine)

Where the excerpt for reads as:

Indicates that the feature request will not be implemented, or that a bug will not be fixed at present time.

with its extended description reading:

A feature request or bug report is considered declined if the report is reviewed and the site developers disagree that the feature should be implemented or the bug should be fixed.

However 's excerpt reads as:

Indicates that the feature request or bug has merit to consider, but will not be implemented or fixed in the near term.

with the extended description saying:

A feature request or bug with this tag is something that has been evaluated as positive on potential, but is not present in the current work timeline. It is also not guaranteed to be implemented - when it resurfaces, the proposal may be re-evaluated and a new decision made depending on how the situation has changed since then.

By all rights, based on the wiki excerpts it looks like that should have had . but my understanding, based on private conversations with staff, is that is only used for things that are part of a long term plan, i.e. absolutely intended to be done, just not soon.

My guess is there is no plan long term or otherwise to get the linked chat issue completed, even though they recognise it would be worth doing. Had it been it would imply that feature was planned, regardless of how far off implementing that plan would be (years, decades, whatever).

Is this how the staff use the tag? Do the tag wikis need updating?

  • 2
    Welcome to the Land of Chaos, where status tags are lost. :) Mar 2 at 15:03
  • 2
    @V2Blast perfect example of the chaos I'm talking about. Tag wiki excerpt of the status-review tag that you applied: Indicates that the circumstances behind a bug report are set to be internally reviewed. Do note, this is not a bug report. It is a support question, or discussion. Everything is a mess. Mar 2 at 15:21
  • 5
    @ShadowWizardHatesOmicron: Relevant MSE post: What posts should be escalated to staff using [status-review], and how do I escalate them? I figured this Q&A, though a support question, could use an official response from staff, since only staff can really answer it (and because there has been confusion around how the tags are used). Though I think that the linked post makes [status-review] one of the clearer tags in terms of how we use it...
    – V2Blast StaffMod
    Mar 2 at 15:24
  • 5
    @ShadowWizardHatesOmicron unfair. The incorrect wording was added by community member(s). The original wording from staff members was clear and unambiguous as Indicates that the report contains merit to consider, but the decision on its approval or decline requires more investigation. This is neither chaos or everything being a mess, it's wording that's not as precise/correct as you'd perhaps like. The intent is still fine.
    – Rob
    Mar 2 at 16:22
  • 3
    @ShadowWizardHatesOmicron we don't live in an ideal world; that much should be pretty obvious based on the past few years of real world events, if nothing else. Chill.
    – Rob
    Mar 2 at 17:14
  • 2
    I suggest also including quotes from the extended tag wikis from each tag, not just the excerpts. Mar 2 at 19:17
  • 1
    @SonictheSaveUkraine-hog I just went to look, they're fairly long and not accurate either? Feel free to edit them in, but I will hold off for now Mar 3 at 1:59
  • Edited in. I'd say that the current tag used is valid, due to the third paragraph of status-declined's extended description: [This tag] can also come up if the bug report is determined to be valid (i.e. not status-bydesign), but the team has decided not to fix the bug for technical or performance reasons, i.e. that fixing the bug would lead to further performance issues or introduce other bugs. Mar 3 at 4:28
  • @Sonic I honestly don't think you, me, or anyone else who does not work for SE can, or should, edit the red tags wiki. We can't possibly know how SE really use those tags, so everything is just a guess, naturally usually wrong. This only leads to confusion when the tags are used against what's written in the wiki, as happening these days. Mar 3 at 7:24
  • 1
    @ShadowWizardHatesOmicron We can, however, look at past uses of the tags and document how they've been used. (The part quoted in this question was added by a staff member, by the way.) Mar 3 at 7:46
  • 1
    @ShadowWizardHatesOmicron we absolutely can know how SE uses those tags, we just need to asks a question on meta about how SE uses... Wait a moment... That's this question 😱 Mar 3 at 9:58
  • @AncientSwordRage e.x.a.c.t.l.y. ;) Mar 3 at 10:00


You must log in to answer this question.

Browse other questions tagged .