5

A status tag was recently added to My support question (more specifically, ). And from my current knowledge, status tags (e.g , , etc.) are used for s and s. So to make sure my question was unusual, I searched for support questions with status tags. My results:

For all the questions:

In total, there are 700+ support questions with status tags. So, is my knowledge incorrect? Or do moderators like to add status tags to support questions? Or is there a post in the meta that I haven't seen that says that status tags are also added to support questions?

5
  • 8
    "do people like to add status tags to support questions?" - No. Please note that those tags are red, and see one of the tags description: "Red status tags can only be applied by moderators and site developers". So it's for their control/workflow
    – hkotsubo
    Aug 1 at 23:41
  • @hkotsubo right. I forgot that the status tags can only be used by moderators Aug 1 at 23:43
  • 6
    Looking at the support questions tagged as completed, most of them seem to be requests for tag changes on Stack Overflow (prior to April 2014 this site also served as the per-site meta for Stack Overflow), which were tagged as completed once the tags were changed as requested. These are tagged as discussions and support questions because they're not bug reports or feature requests for the SE system (see the old tagging instructions at the time). Aug 1 at 23:56
  • 2
    Can be funny (?) if status-review would be added here. Aug 2 at 6:12
  • 1
    There's nothing to review or do tho >_>
    – Journeyman Geek Mod
    Aug 2 at 7:00

2 Answers 2

9

TLDR: We also misuse MSE as a ticketing system.

In a sense - both traditionally and currently MSO/MSE has acted almost like a ticketing system, While the mechanisms vary - from folks keeping an eye on meta(s) actively to the status review tag being linked to the actual ticketing system SE uses internally. Where possible we align it with the roadmap though we sometimes tag posts of broader community interests as well. We also may use these tags, especially on per site meta, to indicate the mod team is reviewing something, or the status of a request, depending on mod culture.

The other status tags allows the community visibility over the status of these posts. Ideally staff would update them, but moderators sometimes retag posts that are obviously talking about resolved issues. With a support tag - completed would indicate that the request made in the question was fulfilled in some way, planned meant they were looking at it and so on.

As such the tags reflect that something has been pushed into the company's radar, and what the decision on said matter is.

3
  • This might explain the status-review added to support questions, however status-completed makes no sense. There was no bug to fix or request to implement. It's just confusing, and might be noise. (non relevant detail added to question.) Aug 2 at 6:08
  • 1
    well if you look at that tag, the support request was fulfilled in some manner. The exact manner would depend on the question? I didn't really want to get into the weeds about it
    – Journeyman Geek Mod
    Aug 2 at 6:51
  • Based on that logic, each and every support question that has an answer should have status-completed tag. Sorry, but I totally disagree with that logic. That is just not how this tag should be used. Aug 2 at 7:00
4

Your question How is the Sandbox archive off-topic? is tagged , but it's also possible to read it as a bug report. The question "Is this situation normal?" implies that if it's not, it should be (bug)fixed. Hence I decided to tag it as . It's the shortest way to indicate 'everything is working correctly' and sometimes, that's all future readers want to know. The alternative is having to read the answers, which takes more time. If you're really bothered by it, we can remove it, but I hope this explanation (and JourneymanGeek's) make a bit of sense.

I see now that the tag info says it should only be used on bugs, but as you discovered, that's just the theory and in practice those guidelines aren't followed.

4
  • 1
    "also possible to read it as a bug report." - so just retag as a bug, and problem solved. Aug 2 at 6:14
  • 1
    I'm not sure if that still puts it in some kind of queue for staff (or that only [status-review] does that now), which would be unnecessary.
    – Glorfindel Mod
    Aug 2 at 6:18
  • As far as I know, the status review tag is what triggers the internal staff queue. Aug 2 at 6:22
  • 1
    @Glorfindel: As Shadow said, I think only status-review escalates it to us in some capacity. We do have a staff tool that lets us see bugs reported network-wide (basically a search/filter for bug -status-* on all meta sites by default, with additional filtering/sorting options – and it shows which staff have responded to which posts already), but I don't know how often that gets used now that we have a standardized escalation process.
    – V2Blast StaffMod
    Aug 2 at 15:13

You must log in to answer this question.

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