The flag seems to put in a close vote as well, but the close vote doesn't flag it necessarily? If that's the case, what's the point of the close button?
122304
When I encounter a duplicate, I have two choices: Vote closing because it is a duplicate, or flag it as a duplicate. What is the difference and should I do both?
110697
Can we implement the low quality flag to be like the abuse or spam flags. So if a certain number of low quality flags are made  on a post (whether it be a questions or an answer) the post is deleted?  This would also relieve *close vote and delete vote queues. *which is a much discussed topic.        related:
85868
When reviewing flags, either from the queue or from the flagged post, I often want to know what the flagger could have done in addition to, or instead of, flagging for mod attention.  Does he have the rep to downvote?  To comment?  To vote to delete?  Knowing this doesn't necessarily affect how I handle the flag, but if there's a possible teaching moment there I use the flag response to point it out.  But I can't find this out unless I click through to the user's profile (unless I already know this user, of course).  Would it be possible to get the flagger's reputation in a tooltip, like what's already done for comments?
67973
I flagged  five days ago because it seems off-topic to me. The question has been closed by a moderator few minutes after.  However my flag has not been marked as helpful (or declined, or disputed) in my flags summary page. It's just like the flag has not been taken into account (screenshot below).    Is a moderator can explain me?
109444
The Off Topic close dialog has a small alignment issue. The link to  is misaligned with the rest of the text on that line.  The problem only occurs when there is a vote count for that close reason.    Not exactly a major world problem, but I thought I'd point it out.  Firefox 23.0.1, Windows 7
18005
My request is simple: Many times, there will be a question where some people feel like it should be closed. At the same time, I'll feel like it's a perfectly legit question, and it should therefore NOT be closed. Right now, I have to wait till it gets enough close votes (which it always does for some reason, as soon as 1 or 2 people vote to close, e/o else decides to vote as well) and then vote to re-open. How about, as soon as there's one vote to close, there should be an option to counter the close vote, something like "vote not to close" or whatever. This would then bring the "Vote to close" number down by one. Only when the vote to close outnumbers the vote not to close by 5, that's when a question is indeed closed. Any thoughts?
73462
Related:    I recently noticed something: The off topic subreason chosen by flaggers doesn't make any difference at all. Specifically, the subreason chosen is not shown to close voters.  Besides, as the "other" reason is unavailable, a lot of cases that aren't covered by the custom off topic reasons aren't flaggable unless you use a moderator flag (which is less useful as it doesn't go into the review queues). This is a gap in the workflow, and not entirely intuitive for flaggers.  I propose that we give the flaggers one close off topic reason (and one migration reason)? It seems like the backend already treats custom close flags as the same.  The most obvious objection here (to me) is that it removes part of the usefulness of the close reasons -- the fact that, for flaggers and VTCers, it's much easier to determine whether or not the question should be closed.   However, this can be solved by nesting the close reasons under the description of a  generic "Does not fit the topic" close reason.    Alternatively, just give flaggers an extra default close reason "This question does not appear to be about $Topic, within the scope defined in the help center."
35712
I've found strange behavior when closing this  - I definitely see that there are 3 closing votes and 2 of them are at "Off-topic" section:   -but there are no explanations on section itself:   -while, normally, it's expected that it will appear. In custom comments section there are also no closing-votes displayed.   Perhaps it's just my browser (which is FF 26 x64 under Win) - so marking this as a "possible bug". Thank you for your attention.
39382
When a question is initially flagged as a duplicate, there is a comment. If the duplicate flag gets enough votes, the question is closed as a duplicate, and the comment is deleted.  Does upvoting the duplicate comment count as a close vote? Does it do anything at all?
69067
While handling flags over the past few days, I've noticed something odd. It seems that when closing a question from the queue using the queue's "Close Question" button, the flag is not marked as handled.  I have noticed this in a couple circumstances. First, by questions I have put on-hold myself; when reloading the queue, or refreshing the question's page, I still see the flags there. Also, I have seen flags requesting closing, and seen that another mod has viewed and closed the question, yet the flag remains.  The only other automatic-handling situation was for deleting posts; this seems still to mark the flag(s) as handled as before; it seems only to be Closing which has this trouble.    Per the comments and further information, it seems this only applies when the post has had a Custom flag on it. That makes sense, and I'll be testing it (for example, on one with only a close flag).  In the meantime, I'll note that if intended, the UI could use some improvement there, as the way is works now once we close the question, it's not apparent that the flag(s) are still present.    Just confirmed with a Low Quality flag that when closing from the Mod Queue, the flag is indeed cleared.
102189
Consider this Low Quality review:    Based on the answer in , it appears that:     Since questions with close flags are sent to the Close Queue, "Recommend Close" basically ends up punting the question from one queue to another.    In the time since I voted to close the question with a binding vote, six people voted to "Recommend Close", then there was one more binding close vote, then three more Recommend Close votes, before it was finally closed.  All told, it took 14 people to close one question.    After a certain number of "Recommend Close" votes, shouldn't that have some sort of extra effect?  Maybe 3-5 "Recommend Close" counts as one close vote?    Or if "Recommend Close" votes after the first vote aren't going to do anything additional, should people with less than 3000 reputation even see questions with a "Recommend Close" vote in the Low Quality Review Queue?  I guess I'm just confounded by how many people had to review the blasted thing.
46191
I'm still getting flack about . I downvoted an answer and added a comment explaining my reason. I was later convinced by other comments that it was not a good reason for downvoting. Upon attempting to retract my vote, I inadvertently locked it in.  The hover-text still (over a year later) says I can "click again to undo". But it's a big fat lie.  My specific problem has been resolved. But, I have stumbled across other questions where users have done this. In keeping with the push to help new users not to discover rules after having broken them, I think this text needs to be a little more aware, a little more accurate.
53250
When I'm using the Stack Exchange mobile view (specifically on my iPhone), after voting to close a question I am also shown the flag count. If I refresh the page afterwards, the flag count disappears and I don't think there is (or should be) any way that a non-moderator should see this.  Take for example . This is what I see before my close vote:    Additionally, the close vote dialog doesn't make it immediately obvious like the desktop version how the close votes are distributed, but this is a lesser issue:    After the close dialog is gone, I get the "x votes remaining" message, and I am also shown the flag count, which I don't think I should be able to see.
100729
System hides an option to flag Very Low Quality in few cases, namely when post is:        Because of that users who already flagged it when none of above conditions applied miss an option to .  Suggest1 to show this flag option to such users so that they could retract a flag.    1 Frankly I won't mind if this gets  because I doubt that it is important. This is posted mainly to document how system behaves and to provide reference for those who may wonder why they can't retract flag in some cases.
44600
I recently got  in the Close Votes queue (). Before I voted to close it, it had 2 votes to close it as a duplicate, 1 vote to close it as "off-topic" and 1 vote to close it as "unclear what you're asking". I voted to close it as "unclear what you're asking".  So at the end, there were two votes to close as a duplicate and two votes to close as "unclear what you're asking". According to , the last close vote will be used to determine the close reason in case of a tie. In this case, the last close vote was mine and the reason was "unclear what you're asking". But it was still closed as a duplicate.  What's going on here? Is this a bug? Is the answer I linked to wrong? Is there a special case for duplicates? Something else?
55514
I'm out of close votes again today. But I still have 100 flags. How do the mods feel about me flagging questions for closure, even though I would be able to VtC myself, if I weren't already out of votes?  Related: How do the mods feel about me flagging a question for closure (a super obvious code-dump, for example), even if I have CVs remaining, in an attempt to preserve my close votes for less clear cut close decisions?
23802
was recently closed (partly thanks to my own vote to close it.) While it was closed as being "off topic", I'm not sure that's actually the case. The poster asked about resources for understanding the facade and decorator patterns. While it's not a perfect fit for SO (e.g. there was no actual code) the reason I personally voted to close was my disdain for the complete lack of research effort made. (A simple Google search turns up a ton of resources.)  I know that downvoting is intended to mark questions that show little research effort (as pointed out in ) but should be a strong enough reason to close?  I find myself voting to close for this reason relatively frequently, so I suppose my two questions are:   Is this a legitimate reason to vote to close, or should I just be downvoting these questions? If it is a legitimate reason, can it be added to the list of reasons for closure? I don't think it fits comfortably in any of the current reasons.