When reviewing a report, this is the question I am asked “Is this post something else or spam?”
This is not a Yes/No question. What does Yes or No even mean in the context of this question?
I suggest this is reworded for clarity. It would also be good if the popup menus were more clearly differentiated as to which one means the message is bad and which one means the message is good.
I’ve seen a lot of weird UX with the new queue, like when a post is rejected before creation it will say “yes” instead of like “Approve”
Also back in my day to indicate a button didn’t immediately act there would be an ellipsis (“Is this post spam?” “Yes…” which leads to delete/ignore/…) so that would be a positive change too
This looks a bug unrelated to the question here, is there an existing topic for this one?
In the OP’s post, yes/no are dropdown menus which take place of the ... next step in the previous layout. the standalone “yes” button in your screenshot should never occur, so it’s something we need to fix.
Can you elaborate what’s confusing about it? the question is formed using the flag types… so the post was likely flagged with “spam” and “something else.” The question is essentially, “do you agree with this flag?” and the actions are sorted based on how you’d answer that question.
“Is this post something else or spam?” — if read as a normal English sentence, the logical answer is always Yes. Either it’s spam or it’s something not spam.
I guess the intent is more like “Is this post flagged correctly?” but it can be hard to see past the literal logic and grammar of the question as it’s written. I expect it to be followed with:
a.) it’s spam
b.) it’s something else
ah I see what you mean now, I wasn’t considering “is this X or Y?” but “is this [list of problems]?” Maybe when combining multiple flag types we have a more generic “Is there something wrong with this post?” text
That sounds like an easy way to make it much clearer.
I don’t think so, I’ll open a report as soon as I can.
Update: as @Moin pointed out this was actually a problem before and was “fixed” but I can still see it (as seen in the screenshot):
That would also partly fix Flag reason conversion to lowercase has unintended consequences - #2 by Moin
Instead of
Ist diese(r/s) Beitrag am thema vorbei oder sonstiges?
where “Thema” and “Sonstiges” should have a capital letter, the new question would not require forcing lowercase on flag reasons. So, I wonder if the question could also be changed for the case where it’s just asking about one flag type, avoiding the enforced lowercase altogether. 
That would have a much clearer “Yes” answer. I know this changed a short while ago and I have found the change definitely negative as far as my being able to quickly say “Yes, its spam and delete and block the user” (as is virtually always my answer).
“Approve” seems still problematic terminology since the question would then be - am I approving the post or the flag?
Something like: “is there something wrong with this post?” “Something is Wrong>”, “Post is Good/Fine/Acceptable>” might be better questions and menu labels. Yes/No for buttons are generally a bad idea as far as UX goes - active button names are usually better.
Thanks!
