Is the disputed flag handled any differently in the new triage review queue. I marked this question as very low quality, after choosing unsalvageable and this was disputed. From what I have read, if a question is edited, this puts the flag in dispute, but this question was not edited. I have no complaint, I just want to understand what is going on, as the triage queue seems like a really good initiative, so I want to help as positively as I can.
closed as off-topic by Glorfindel, rene, Robert Longson, ale, user58 Jan 22 '18 at 15:52
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – Glorfindel, rene, Robert Longson, ale, user58
The short answer here is that when a question is triaged as anything other than Unsalvageable, any pending Spam, Offensive, Very Low Quality or Close flags will be marked Disputed. This is done to prevent the queue from potentially sending questions in three different directions at once (mod flag queue, close review queue, and whatever the intended destination was).
Note that close votes are not affected; if you're trusted to vote, your vote can only be removed via the normal aging mechanisms.
Additional complexity in your scenario
This answer got a bit weirder when I realized that you'd flagged the question as very low quality. See, that wasn't supposed to be an option here - eventually, VLQ flags are gonna send questions into Triage, so having that as an option there doesn't really make a lot of sense. That was in the original design, but... I kinda overlooked it when testing.
When I mentioned this to Geoff, he noted that it'd be possible to make the flag unavailable on the question page itself if the question was currently being triaged, making this all a bit more consistent and side-stepping a few even weirder scenarios...
Changes to VLQ flag availability
So as of a few minutes ago, Very Low Quality won't be an option from within Triage review or from anywhere else while a question is being triaged. We're also taking this opportunity to be a bit proactive with another change that'll be necessary soon: Very Low Quality won't be available for questions that are currently undergoing Close review either.
This moves VLQ one step closer to my intended purpose: catching awful questions that slipped through the cracks somehow. We'll see how that works out in practice...
Marking a question as VLQ is there to push it into the Triage queue (now). It's there to say that some sort of action is needed in that queue.
It doesn't make any sense to use that flag from the Triage queue. You're flagging an item in that queue as needing to to into the queue you're flagging it from.
It shouldn't even be an available option from the "unsalvageable" menu, as it has no sensible workflow from that position.
If you think that the post is unsalvageable, then from the Triage queue you should be voting/flagging it for closure, or flagging as spam/offensive/some custom flag.