5

I've recently noticed that items in the Low Quality Review Queue aren't getting kicked out of the queue after one "looks good review"

Compare from a month ago:

historical

https://softwareengineering.stackexchange.com/review/low-quality-posts/44689 (not the same one as the previous, however showed same sequence of items)

To something that was done today (though hasn't been yet):

today https://softwareengineering.stackexchange.com/review/low-quality-posts/47273

Note the multiple looks good and further reviews needed.

I want to point out that both reviews start out with one recommend deletion and then have one followup look good. The historical one completed the review when the "Looks Good" was selected.

The modern one (now completed) was not completed even after multiple Looks Good (I don't know if it had left the queue when the third one was chosen).

Is correct? or a bug?

Improve this question
8
  • Perhaps it considers flag weights.
    – Travis J
    Dec 17, 2013 at 23:10
  • @TravisJ Flag weight doesn't exist anymore.
    – Adam Lear StaffMod
    Dec 17, 2013 at 23:15
  • @MichaelT can you link to the reviews in question for moar context?
    – Adam Lear StaffMod
    Dec 17, 2013 at 23:16
  • @AnnaLear - Doesn't exist in the user's profile, doesn't exist internally in the system, or both?
    – Travis J
    Dec 17, 2013 at 23:17
  • 1
    @TravisJ Both. It was taken out some months ago.
    – Adam Lear StaffMod
    Dec 17, 2013 at 23:18
  • @AnnaLear I've added the links. The link from animuson suggests changes in flagging had an effect on the queue. I can't see the flags on the post, it could very well play into the equation also with winterfest increasing site participation and flagging (thus needing more looks good to dequeue?).
    – user213963
    Dec 18, 2013 at 0:08
  • @MichaelT The first review had no flags on it at all and the second had 4 VLQ flags. Not sure off the top of my head how many reviews would've been required to handle it without ChrisF's binding delete vote.
    – Adam Lear StaffMod
    Dec 18, 2013 at 0:11
  • @AnnaLear thus the difference in dequeueing. I'll chalk it up to "difference in participation from winterfest" -- it would be most interesting to do a report on "flags cast" (for example) for different time periods seeing how the hats influenced various behaviors. You want to status-by-design this one then?
    – user213963
    Dec 18, 2013 at 0:14

1 Answer 1

Reset to default
12

It depends on the number of flags. If there is only one very low quality flag on the post, then it only takes one Looks Good decision to kick it out. If there are two, it takes two, three takes three, and so on. Likely that post had more than two VLQ flags on it, which kept it in review past the normal actions.

Straight from the Shog:

If more than one VLQ flag accumulates on the post before the review has ended, a number of "Looks Good" responses equivalent to the number of flags is required to dequeue it. ...

Once reviewed, further VLQ flags do not re-add the post to the queue. ...

Improve this answer
1
  • 2
    That appears to be something from July. The functionality appears to have changed between mid November and mid December. Though, it could be because of flags (winterfest, people flagging for hats increasing that site participation?).
    – user213963
    Dec 18, 2013 at 0:07

You must log in to answer this question.