It seems like recent changes to the way flags are handled has introduced some strange behavior.

A little bit of background

Users who don't yet have the reputation to vote to close can flag for moderator attention, select "It doesn't belong here", and then select a close reason from the same set of choices available to close voters. These flags get added to the 10K queue, where they sit for a little while - if a 10K user agrees and votes to close, the flag is dismissed (as helpful) by the Community user. If nothing happens, the flag eventually "graduates" to the moderator flag queue...

And therein lies the problem

If a moderator responds to one of these "close" flags and closes the question without manually dismissing the flag, the Community user dismisses it as "helpful" and the moderator's flag handling count is not increased!

A few months ago:

enter image description here


enter image description here

I would expect the flag, once having been shown in the moderator queue, to behave as any other flag - action on the post that results in automatic dismissal also attributes the dismissal to the moderator who dismissed it.

  • @Nine Shog, it doesn't look like close flags are the only ones affected by this. It behaves the same way for any flag for moderator attention (including VLQ, custom reasons, etc.) Dec 17, 2011 at 20:26
  • 5
    Community taking all the credit again?!
    – studiohack
    Dec 17, 2011 at 20:55
  • It's definitely not all flags, @Null - but you're right, it does seem to include more than just the close-flags.
    – Shog9
    Dec 17, 2011 at 22:02
  • 3
    @Rudolph, Community is at 530 on SO now (almost 8k on another site), but that used to be much more. Yes, beware: someone is using its reputation for bounties! ;-)
    – Arjan
    Dec 18, 2011 at 1:20
  • Where did you take those screenshots? Dec 18, 2011 at 5:09
  • We're looking into this. May 23, 2012 at 1:55

1 Answer 1


I'm going through and ensuring that all places where flags are dismissed give proper credit to the moderator doing the action.

This will be fixed in the next build.

You must log in to answer this question.

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