237

All good things must come to an end and so must the review queues project. This project would not have been successful without the community. Thank you all for the hours of reviewing, testing, and sharing your feedback along the way. With that said, this will be our final major release. In this post, I’ll summarize the changes we’ve made to the overall queue workflows and the specific adjustments to the Reopen votes queue.

Changes to the First posts queue

First posts → First questions AND First answers queue

  • To avoid context switching, and recognizing that asking and answering require slightly different skill sets, we are creating two separate queues to handle the individual post types.
  • The purpose of these queues remains the same – helping new users learn how to use the site. With that in mind, reviewers will be able to choose from three actions: Looks OK, Edit, and Share feedback.
  • It can take time to develop the skills to write a good question or answer. A user’s first few posts may require extra attention and to help new users get the hang of things, First questions and First answers will accept up to three posts per user if their first couple aren’t successful.
  • Reviewers are encouraged to leave comments for the post-author, but now they can also choose from a few options of canned feedback which will appear as a comment from the Community account.

Canned feedback options appears in modal Canned feedback appears as a comment from Community

Changes to the Reopen votes queues

  1. “Significant edit” option

    Post edit screen with significant edit option

    • This feature appears when editing a closed question and allows editors to indicate if they’re making a minor edit (i.e. grammar, spelling) or a significant edit. By submitting an edit for review, the editor agrees that their edit attempts to resolve the question’s close reason(s) and should be considered for reopening in the Reopen votes queue.

    • Once a significant edit has been submitted, editors are still able to return to the edit screen and make further adjustments. Significant edit status will also be indicated in both revision history and post timeline pages.

    Post edit screen with significant edit submitted

  2. Significant edits in the Suggested edits queue

    • Users who do not have enough reputation to submit an edit outright will have their significant edits go into the Suggested edits queue accompanied by a post notice.

    Significant edit in Suggested edits queue post notice

    • Actions in the Suggested edits queue will change based on whether the edit has been flagged as a Significant edit. In the case of a Significant edit, reviewers will be able to Approve and reopen or Approve and leave closed.
    • It takes two approve votes (any combination of Approve and reopen or Approve and leave closed) to remove the task out of the Suggested Edits queue. If at least one of the votes is Approve and reopen, a new task will be created in the Reopen votes queue.
  3. Leave closed reasons

    • If a Reopen votes reviewer elects to leave a question closed, the reviewer will be presented with a “Leave closed reason” modal (similar to the close reason modal) that will return feedback to the editors. For example, if a question was originally closed because it lacked details, it may still require further details even after an edit, or new issues with the question might present themselves like asking too many questions at once.

    Reasons to leave a question closed appear in modal

    • In addition to inbox notifications, the closed question’s post notice will also be updated with more information.

    Post notice updated with new close reason

  4. Multiple opportunities to send question for review

    • We’ll be launching this feature without any limits – users will be able to submit multiple edits on individual posts. We’ll take a look at the data in a few weeks to see if any abuse of the feature has occurred and take mitigation steps as needed.

    • [Stack Overflow only] Reviewers will not see posts that

      1. they’ve voted to reopen since last closed, and
      2. voted to close since the post was last edited.

      Moderators are exempt from this restriction.

  5. Bug fix: “Don't cause the reopen vote of the user, whose edit pushed the closed question into the reopen queue, to invalidate the review”

    This bug fix is also included as part of this release. You can read Kyle’s detailed response here.

Other changes to the Review queues

  1. Turn off the Help & improvement queue

    • H&I has been our least productive queue. Over the last 90 days, only 9 tasks went into the queue each day on average, compared with 2,215 for First Posts (our busiest queue) and 188 for Reopen Votes (our second-to-last busiest). Consequently, this queue will be turned off. It will remain in the listing until its current items are exhausted, and will then be removed. History for and badges awarded from this queue will remain as they are.
    • With the addition of the First questions queue, we expect that questions with potential can get the same assistance they need more quickly.
    • Questions that would have ended up in this queue from Triage (with a Needs community edit action) will now enter the First questions queue.
  2. New actions for Late answers queue

    The Late answers queue has been successful in identifying and removing low quality posts, repeat answers, and spam. Reviewers were able to take any number of actions on a task, so the objective of this queue wasn’t all that obvious. To clear up any ambiguity and focus on identifying problematic answers, we’ve defined three actions: Looks OK, Edit, and Delete.

  3. Keep Triage queue (Stack Overflow only)

    • Triage will continue to handle questions only.
    • Triage will be available on all sites, but only turned on by default on Stack Overflow. Have a meta discussion and ask a moderator to if your site wishes to add the Triage queue.
  4. Name change: Low quality posts → Low quality answers (Stack Overflow only)

    This queue will continue to handle answers only.

  5. Misc. We won't issue new Reviewer or Steward badges for the queues that were turned off, but this won’t have any effect on badges already earned in these respective queues.

    Along with all these changes, here is an updated visual of the Review queues map –

    Flowchart of review queues

What about issue X, Y, Z?

As mentioned earlier, this is our final major release. We will not be pursuing the proposed suggested tasks feature at this time. We didn't feel that it was going to significantly increase curation activities on the site and therefore didn't warrant the high development cost.

There are still a few outstanding issues related to suggested edits that have proved to be technically challenging. We’ll respond in those original Meta request posts as soon as we decide on a course of action.

Feedback

Please leave your feedback and any bugs you may discover related to this release below this post. We will be monitoring this post until Friday, September 10th. Report any further issues after September 10th as new questions on Meta.

45
  • 71
    "appear as a comment from the Community account." - Neat!
    – Nick
    Aug 26 at 13:50
  • 6
    "Looks OK, Edit, and Delete" for Late Answers. Does that mean 500 reputation point users now effectively have Delete privileges? Or does that send the post to another queue? Aug 26 at 14:34
  • 10
    @Xnero You're posting a lot of comments that are already mentioned in answers or that should be answers - please don't use comments for this purpose.
    – Catija StaffMod
    Aug 26 at 15:01
  • 19
    As a side note, in SOpt lots of new messages are in English. I know there's a "solution" to this (go here and translate), but honestly, I'm getting tired of this "SE changes site -> messages are in English -> community translates" cycle. I'd love to see a better solution, that doesn't require the community acting after the change is made.
    – hkotsubo
    Aug 26 at 16:19
  • 5
    Too bad this is featured roght now. I'd rather see Aaron's post about removing the top bar preferences featured :(
    – Luuklag
    Aug 26 at 17:37
  • 12
    Late Answers requires a downvote before being about to select delete. I love wasting my rep on DVs. I'm sure everyone wants to waste 20/40 rep going through the queue each day. Absurd. Aug 26 at 18:31
  • 9
    @JourneymanGeek posts with 0 score can receive delete and recommend deletion votes (at least in the old queue... I'm not clear yet on exactly how the new one works, but I am 100% on board with encouraging people to downvote when voting to delete. One should always be readier to downvote than to delete!)
    – Zanna
    Aug 27 at 8:06
  • 6
    @Zanna I have reservations about these kind of statements. I've seen more irresponsible drive-by voting than perhaps you'd imagine. Not just that, but also taunting users in the comments who haven't earned enough rep to downvote back. It only takes 1 high-rep user to throw a low rep into the question ban.
    – bad_coder
    Aug 27 at 23:24
  • 7
    @TylerH - Thanks for the info. I respect the fact that the new design can be useful on other sites where I'm not active. I was trying to say that it'd have been better if the old response options weren't completely removed - they could have been kept along with the new design.
    – TRC
    Aug 28 at 4:07
  • 5
    @bad_coder What do you mean? I said one should be more willing to downvote than to delete. If one thinks a post should be removed from the site altogether, one should surely be willing to downvote it. Would it be less bad if instead of casually downvoting, people casually delete-voted?
    – Zanna
    Aug 28 at 4:37
  • 23
    Did you even test this on non-tech sites? Why does it post comments about code on humanities sites??? Aug 29 at 5:55
  • 12
    @curiousdannii That's hardly the only such wording blunder. Here's another: apparently now all answers must be "solutions".
    – tchrist
    Aug 29 at 15:23
  • 20
    I initially upvoted this because there are some good things here, but I've changed it to a downvote after working in the new First Q&A queues. The number of options in these queues is severely limited -- I keep having to perform actual moderation (like vote to close) and then click "Looks OK" to finish the review for a post that is clearly not OK. I understand that there will be some bugs at first, but the workflow seems like it was designed by people who don't have much (if any) experience actually reviewing first posts -- many of which are not OK and/or need more than an edit or "feedback".
    – Null
    Aug 30 at 15:40
  • 11
    You know, if you guys want, there's a significant number of us here who would be happy to beta test this stuff out and give you some real user/curator feedback before you 'Final release' it out onto the entire broad spectrum of sites like this.
    – ouflak
    Aug 31 at 15:51
  • 7
    @TobyHarnish, Meta sites aren't just for questions. They are also for announcements, regular updates, and site discussions.
    – ouflak
    Aug 31 at 20:42

119 Answers 119

15

Verified in first answers, not sure if it holds elsewhere but I imagine it does.

I stumbled over a link-only answer, and my first instinct is to downvote and flag. Voting is fine. The flag menu, however, acts as if the post is deleted (which, in this case, it was), only giving "in need of moderator intervention". Only deleted posts give one option, which is a dead giveaway that the post is an audit.

Aside being a dead giveaway that the post is an audit, combined with the lack of being able to flag and then go on to "I'm done" means there's not a sane way to end the review, even if the flag dialog was present. I've flagged a couple real answers and I have no idea what to press afterwards. There's no applicable feedback, "looks OK" is wrong, and so is edit. Allegedly, this part is supposed to be fixed, but I don't see any change in the available options, and flagging isn't enough to complete the review (which is a massive regression, in my opinion. You used to be able to vote and flag, and pick "I'm done" to move on).

image showing the flag popup in first answers only containing "in need of moderator intervention"

Ended up clicking "share feedback" just to end it, which also doesn't make sense as a pass case for this particular type of posts given the current feedback options. There's not really any good way to handle audits at the moment, though. Here's the audit in question (10k+? on Stack Overflow), for anyone interested.

3
  • That also holds true for blatant never-to-be-on-topic first questions, such as identification questions on Movies.SE
    – Jenayah
    Aug 30 at 6:11
  • This has at least partially been addressed now that the "Other action" option is there, but the "ending a review after a flag" problem sort of still exists, pending the solution to this issue.
    – zcoop98
    Sep 15 at 20:29
  • 2
    I'm going to mark this as completed as we've added back in the ability to complete a review after finishing another action. I also fixed the bug related to the other action option that's referenced above. I realize that it's a giveaway that the post is an audit, but that particular issue we're going to defer.
    – kristinalustig StaffMod
    Sep 17 at 15:51
14

https://stackoverflow.com/review/first-answers/29670070

After flagging:

enter image description here

enter image description here

I got the 'Thanks. We'll look at it' banner. And that's it.

I also left a comment, yet still have the 'Share feeback' option available. I had no choice but to Skip this as there was no other valid option.

4
  • 5
    Already reported for the "First questions" queue: meta.stackexchange.com/a/369037/348196
    – 41686d6564
    Aug 26 at 19:22
  • Very related, for first answers that are NAA like this: meta.stackexchange.com/a/369036/165261
    – Ryan M
    Aug 26 at 19:23
  • What's the point of your edit? If you tried to just bump with "empty" edit, that's a wrong way. Aug 31 at 11:51
  • I'm just picky like that. I hate leaving words out, and am constantly reviewing my own posts for grammar or other errors (as well as posts by others). It's just my nature. And it wasn't an empty edit. I added the word 'banner'.
    – ouflak
    Aug 31 at 11:53
13

Don't know if you are aware of that but currently, Triage blocks questions from getting to close queue for about a day average. I think this is a bit too much:

...we get the situation when system correctly and quickly detects most troublesome questions and then, essentially shields them from getting to close queue - for a full day average, go figure.

This is really really weird. The way how things work now, system essentially incentivises askers of poor questions to pay money for fraudulent release of asking limits. Seeing multiple poor questions hanging open and seemingly unattended for days can only convince them that their ban is mere misfortune and that it makes sense to try their luck again...

I would appreciate if you could do something about that.

Probably least effort consuming option to address above issue would be to allow questions getting to close queue while they are on triage (possibly with some reasonably small delay, if you prefer).

3
  • 1
    Sounds like if I vote to close a question that's in the triage queue, it should go immediately to the close vote queue (and either skip triage or just be in both). Aug 26 at 21:28
  • 3
    @doppelgreener if you remember, initial design of the triage assumed that triaged questions aren't visible to anyone except for triage reviewers. The fact that it currently is blocked from getting to any other review naturally follows from this initial (unfortunately abandoned) design
    – gnat
    Aug 26 at 21:33
  • @kristinalustig just in case if you prefer to have a separate feature request for this matter - it is linked in my post from words "a bit too much"
    – gnat
    Aug 27 at 13:43
13

The removal of the "I'm Done" option from the Late Answers queue raises some issues:

We can no longer:

  • Vote up/down
  • Flag as Rude/Spam or for moderator attention
  • Leave a comment

As a review action.

If this is not intentional - please add an "I'm Done" button or anything similar.

If this is intentional (maybe these are not intended to be actions in this queue and I missed that) - then this queue falls back to be identical to the Low Quality Answers review queue. Is this intended? It certainly feels like a weird and confusing duplication. You said, regarding the Late Answers queue:

The Late answers queue has been successful in identifying and removing low quality posts, repeat answers, and spam. Reviewers were able to take any number of actions on a task, so the objective of this queue wasn’t all that obvious. To clear up any ambiguity and focus on identifying problematic answers, we’ve defined three actions: Looks OK, Edit, and Delete.

To me, the objective of the queue is even less obvious now. If its purpose is to remove low quality posts - we already have a queue for that. If its purpose is to remove repeated answers - we didn't really get the tools for that (not NAA and none of the recommend deletion options applies). If its purpose is to remove spam - we could already flag spam before and it doesn't really require a deletion option (enough flags will delete the post anyway).

So, what is the current objective of the queue?

13

Message for reaching daily quota is blank for the "First questions" queue

Today, I reviewed twenty First questions and as much Suggested edits at the Mathematics Stack Exchange site. Now, when I look at Review queues page, I see that there is a light blue rectangle below Suggested edits (see the picture below), in which it is written “Thank you for reviewing 20 suggested edits today; come back in 8 hours to continue reviewing.” So far, nothing is new. But below First questions there is also a blue rectangle… with nothing written in it.

enter image description here

4
  • 4
    Been seeing a lot of those...
    – Ollie
    Aug 27 at 15:59
  • 2
    Reproduced for me. Aug 27 at 21:48
  • 2
    Hi there - this should be fixed. Please let me know if you're still seeing this blank message.
    – kristinalustig StaffMod
    Sep 14 at 16:10
  • 1
    @kristinalustig No, I don't see those blank messages anymore. Thank you. Sep 14 at 16:14
13

In the new First Questions review queue, if you cast a close vote (i.e., by flagging a question) and it passes the threshold to actually close the question, then it will refresh the page to include the closed message, and add:

You are not able to review this item

It makes perfect sense that a question that is now closed would be removed from the review queue. And it makes sense to provide immediate feedback to the flagger that the question is now closed. But I would also expect that voting to close a question would qualify as already having reviewed that question.

I assume this only applies to people who have the cast close and reopen votes privilege (3,000 reputation).

enter image description here

1
  • 1
    FYI: While this is still marked as status-review, I believe this is now status-completed. At least, on Stack Overflow it no longer completes a review when a question is closed, and allows the reviewer to continue with the new Other Action option. Sep 15 at 20:27
12

Undo accidental wrong feedback

I stumbled across question that needs to provide some codes, so I clicked the share feedback button:

I wanted to click "Question needs some code", but I accidentally clicked the "question is too broad" option and shared the wrong feedback to the user.

Is there a way I could undo the feedback? Because I can't seem to do anything with the comment.

3
  • You can flag the comment as no longer needed, that way a moderator can delete it. Otherwise the comment is owned by the Community user, and thus not modifieable by you.
    – Luuklag
    Aug 27 at 8:32
  • @Luuklag i just tried to review a post and flag the community comment and nope i cant flag the comment. It says "This comment will be automatically removed when post is corrected" when i tried to flag it
    – SO_user
    Aug 27 at 8:36
  • 1
    I have a request about this. Hopefully, it'll be considered. - "nope i cant flag the comment": This has also been reported.
    – 41686d6564
    Aug 27 at 8:38
11

One quick thing, everything looks good on a glance through! Can the First Posts queue be moved out of the way to a section at the bottom like what is done with "Retired Badges"? Similarly "First Posts" now probably doesn't warrant showing in the review queue drop down from the top bar.

2
  • 8
    It'll be moved out of the way in a couple of weeks. We're making sure that the queue gets fully emptied out before we fully disable it so that no posts get lost in the void.
    – kristinalustig StaffMod
    Aug 26 at 15:12
  • At least on Stack Overflow, this queue is no longer displayed, so I believe this is now completed. (Acknowledging it may still persist on other sites where I don't yet have reviewer privileges?) Sep 15 at 20:31
11

On Stack Overflow, if I go to the First Questions or Answers queue, I see this:

enter image description here

Because I don't have the required reputation to review in that queue. But the empty blue banner should look like this, as it does in the other queues there (which I also don't have access to):

enter image description here

As it does in the other queues, e.g:

enter image description here

This also happens if a sub-X reputation user looks back at previous review tasks such as this, which are useful if you need to flag as NAA-, spam, etc. Again, this only happens with the First Answers or Questions review queues, not the Late X ones.

2
  • 5
    Good catch, we missed implementing this message for the new queues. Getting that in today. Thanks!
    – kristinalustig StaffMod
    Aug 26 at 14:46
  • 3
    Just pushed this fix this morning so it should be live either later today or Monday.
    – kristinalustig StaffMod
    Aug 27 at 12:49
11

Phrasing nitpick(s):

The Help center page for the Low quality queue says:

Note: On Stack Overflow, low quality answers are exclusively handled in the Low quality answers queue. You will not see questions in this queue.

This sounds like it's saying that the Low quality answers queue is the only place that handles low quality answers (when really, answers are also handled in other queues), when really it's that the queue only handles answers. It should probably be something like:

Note: On Stack Overflow, the Low quality answers queue exclusively handles low quality answers. You will not see questions in this queue.


Also, ideally "Low-quality posts" and "Low quality answers" would be hyphenated the same way. I think the technically correct answer is hyphenated, but it's really the inconsistency that bothers me here.


Yes, these are both super nitpicky.

8
  • Minor nitpick: These are too nitpicky, but OK anyway.
    – Ollie
    Aug 26 at 15:14
  • I’m I the only one that thinks the capitalization of Low-quality is weird? If it’s a name, the entire name should be capitalized yeah? And yes, I’m a certified class-A nitpicker, and no, I don’t think think this feedback is super nitpicky, but I may be the minority opinion :)
    – ColleenV
    Aug 26 at 15:37
  • 1
    I agree with that feedback - fixed.
    – kristinalustig StaffMod
    Aug 26 at 15:41
  • 1
    @ColleenV Our styles require sentence case for headings - so we only capitalize the first word.
    – Catija StaffMod
    Aug 26 at 15:58
  • But it’s not sentence case to capitalize in the middle of a sentence…? It should be set off in quotes or something if you aren’t marking it as a name of something with caps. “ On Stack Overflow, low quality answers are exclusively handled in the Low quality answers queue…” The point of punctuation and capitalization is to convey information, and within a sentence your style fails to do that and looks like a mistake. A name is not a heading. @Catija
    – ColleenV
    Aug 26 at 16:06
  • The "Low quality" answers queue is the name of the queue - with that exact capitalization. It's out of context in the sentence but I don't know that means we should change how we capitalize it. We're duplicating the heading on the page when we refer to it as an entity rather than merely talking about low quality answers in general. @ColleenV We do this pretty consistently, even if it's not common elsewhere.
    – Catija StaffMod
    Aug 26 at 16:11
  • I am confused by the quotes around “Low quality”.. is that the entire name? Headings aren’t names. You don’t use headings in sentences without setting the off from the rest of the text. Names should be capitalized so people know which words are part of the name and which words are part of the sentence. I’m pretty sure that’s not controversial orthography. @Catija
    – ColleenV
    Aug 26 at 16:19
  • 1
    And, if you’re just using attributives, none of it should be capitalized. It would be fine to write low quality answers, close, reopen, and first posts queues.
    – ColleenV
    Aug 26 at 16:29
11

Can the 'Edit' option be disabled if you don't have the privilege to edit all posts and suggesting an edit is not possible (because the suggested edits queue is full, or you have already too many pending suggested edits)?

1
11

Anonymous comments: They're bad

The thing I like about reviewing on SE, and why I think it works so well, is that it's human. You can ask what's wrong with your post, and quite often get helpful feedback pretty quickly. There's transparency, so you can see exactly what's going on with your post (and who's doing it).

Giving reviewers the option to post anonymous feedback goes very much against this. It sounds like a good idea on the surface, but all it does is introduce issues. When I comment under a post with things that need to be fixed, I have never once had second thoughts because of worries about my name being associated with that. I put a lot of effort in to ensure my comments are helpful, and if I'm asked for clarification I want to be there to help.

Anonymous comments mean the feedback given will always be a bit too vague to really be helpful. One size fits all doesn't fit anyone. Even worse, if the post author cares enough to try to improve it, they can't reach me to get help doing that. To add on to the problems, if these comments are misused, there's currently no way to flag them (as far as I can tell). That's not rare either, I've seen it multiple times already (not maliciously, just incorrect usage).

If automated, useless comments become the norm for reviewing, it'll only reinforce the idea that SO is unwelcoming to new users. Robots are...robotic. Nobody who's new to the site wants to be greeted by being told there's something generally wrong, without being told or being able to ask for specifics.

If these comments were only ever used when appropriate, they'd be fine. But the problem is, the people who use these canned comments often will be the same people who won't take the time to actually weigh whether or not leaving specific feedback would be better. It just gives reviewers the option to be lazy, in a part of the site where laziness will 100% lead to a worse site all around.

This feature feels like a poorly thought out tool to help review grinders grind faster, and it doesn't feel appropriate for any site other than SO (where effiency and quantity of reviews is necessarily much more of a priority than other sites). Please, please get rid of it.

6
  • 1
    I'm of two minds on this. On one hand, I completely agree: these comments are often not very good. On the other hand, new users can't see close votes on their questions, so they lack the feedback that someone thinks something is wrong with their question until it's closed (which can take a long time, delaying the feedback cycle). So getting them some feedback sooner is good, and at least the canned comments are better advice than what people post themselves ("What have you tried so far?", "Please read How to Ask", "SO is not a free coding website", etc.).
    – Ryan M
    Sep 3 at 5:51
  • 4
    Perhaps the answer is just that we need more canned comments, to match the expressiveness of the close reasons. The low-quality answers queue (mostly) handles this well: there are canned comments for (most of) the most common issues. Expanding the comments (and making them site-specific, like close reasons are) would go a long way to making them a bit more useful.
    – Ryan M
    Sep 3 at 5:51
  • 2
    I agree with @RyanM, although I disagree that the close reasons are expressive enough. Canned feedback wouldn’t be so bad if they were less terse, and if we could “mix and match” instead of have to pick just one piece of feedback to give.
    – ColleenV
    Sep 3 at 10:27
  • 1
    @RyanM The problem is, on SO it might be normal to see somewhat useless comments by reviewers (like "What have you tried so far?"). But on other sites, where reviewers should be able to take much more time to give personalized and useful feedback, these canned comments just give reviewers an option to quickly and easily give that exact sort of bad feedback. Site customizability for the comments, and more variety, might help the issue a lot, as long as other issues like not being able to flag or reply to the comments are addressed. Sep 3 at 13:27
  • @RyanM "need more canned comments" - oh, you know, like the extensive lists folks acquired using the famous ARC userscript, for example? :) As an idea, SE could examine what SOCVR serves (not saying that every comment template is gold, but still...). Sep 8 at 14:39
  • 2
    It doesn't matter if the site it big or small. If one wants to review, then one should review, not get it done as fast as possible using a canned comment that doesn't even help the user that the comment is intended for. Sep 8 at 14:47
11

Answers I have already reviewed in the First Answers queue reappear for me in the Late Answers queue. I believe this is not the intended behaviour, since in the past an answer I reviewed in the First Posts queue would no longer show up in the Late Answers queue for me. In any case, it does not seem to make sense for a single user to review the same post twice.

10
11

In the popup and the Help Center page for First Posts, mention that it's retired (and add links to its successors).

1
  • First Posts queue help center page has been replaced by First questions and First answers, and if people go to the First posts review queue, they see a message that the queue has been retired.
    – Anita Taylor StaffMod
    Sep 14 at 21:11
11

When I follow a post, and Share Feedback in one of the new queues, Community posts a comment on my behalf. Because it's a comment not posted by me, I immediately get a notification in my inbox. Could those be suppressed please?

4
  • 1
  • 1
    Re: This and other answers concerning the comments from Community: Maybe the Bot is looking for the Pundit badge? Aug 29 at 20:11
  • Looked into this today, and I'm going to defer it for now, as it would take a decent amount of work and introduces complexity to what I'm pretty sure is an edge case (in that, I'm assuming you don't follow every question you share feedback on). Please let me know if I'm mistaken and I'll revisit.
    – kristinalustig StaffMod
    Sep 17 at 19:58
  • @kristinalustig no problem, it's just a minor inconvenience.
    – Glorfindel Mod
    Sep 17 at 19:59
10

I can't perform the most important action in "First answers queue". I can't flag the answer for deletion or vote to delete it myself. How can I push the post into "Low Quality Answer" review?

6
  • 3
    I guess your and this answer is same so there was no need of this answer I feel Aug 26 at 14:22
  • Does this actually say "Del-pls" or did you change that for the screenshot?
    – Anonymous
    Sep 1 at 20:24
  • 1
    @Anonymous It does say. I forgot to disable userscripts for this screenshot.
    – Dharman
    Sep 1 at 20:30
  • @Dharman Just curious, which userscript is that?
    – Anonymous
    Sep 1 at 20:32
  • 1
  • 1
    The post menu is fixed for this queue and you should be able to flag and then mark yourself as having completed your review.
    – kristinalustig StaffMod
    Sep 8 at 14:28
10

/

Let individual sites decide whether they are a "code-related site" for the purposes of the code-specific canned Community comments

kristinalustig remarked that the code-specific canned Community comments are supposed to be available only on "code-related sites". However, it is unclear to me how it is determined whether a site is code-related. I'd like this to be an option that the sites can decide for themselves, as it is not always obvious whether a site prefers their posts to contain code. For example, posting code should generally be avoided on Computer Science. While a site probably has to decide only once whether they want to be 'code-related', it would be nice if this is a setting that e.g. the CM's can touch.

5
  • 5
    And, I suspect the sensible default, amusingly enough should be that sites are not code related. Citation needed, but I'd bet a sock on it
    – Journeyman Geek Mod
    Aug 28 at 15:18
  • 1
    CMs can already touch this. I think that Catija is planning on communicating with site mods about this, but it is definitely configurable (not sure if status-completed is the most appropriate, since it is already fulfilled. whatever.)
    – Yaakov Ellis StaffMod
    Aug 30 at 12:31
  • @YaakovEllis I couldn't tell whether this was a configurable setting, due to the bug that enabled the Community comments on all(?) sites. So I wanted to check whether this was done. Thanks for letting me know. Aug 30 at 14:06
  • Here's a Physics meta question about a Community comment that mentions code: physics.meta.stackexchange.com/q/13790/123208
    – PM 2Ring
    Aug 30 at 21:34
  • @YaakovEllis, Still haven't heard anything about how to 'configure' this. Is this planned?
    – ouflak
    Sep 7 at 10:16
10

On the Code Review site one of the options for First Questions is Share Feedback. It has 2 options that mostly only represent Stack Overflow. The old workflow allowed any comment from the reviewer to be used as shared feedback but that is no longer an option. There are more reasons on Code Review on how a question can be improved.

The Community comments don't really represent the CR community and I can't flag it for moderator attention, and the moderator can't delete the comment.

I see this as a bug.

4
  • You mean a diamond moderator cannot delete the comment by Community? Aug 28 at 16:53
  • 3
    @Unconsidered Exactly, a duly elected moderator can not delete the comment by the Community.
    – pacmaninbw
    Aug 28 at 16:54
  • On Stack Overflow at least, I can flag one of those comments for moderator attention. Aug 28 at 17:03
  • 2
    @Unconsidered Opening the flag dialogue does not seem to be the issue. Flagging the comment (by pressing the "Flag comment" button) seems to be the issue.
    – Peilonrayz
    Aug 28 at 18:58
9

Display site-specific close reasons in the Reopen queue

When reviewing a question that was closed for a site-specific reason, the display in the reopen queue simply shows (e.g. on Stack Overflow):

enter image description here

without stating if it was closed for "seeking recommendations", or for "needing debugging details", etc.

This means if I decide to leave the post closed, I need to navigate to the post in order to see which reason was used, in order to decide whether "the original close reason was unresolved" or if I need to pick a different reason.

These additional actions are time consuming. Also, I've been tempted to just choose "the original close reason was unresolved" without verifying what that was, which is not ideal.

Please display this information on the page itself, preferably just below the above message.

9

We have a problem at SO.es (I supposed Ja, Po, and Ru has the same issue)

On the first question queue, we have only 2 motives to close a question...

But in all international sites, we have another problem.. question that are not in the official site language...

So we need a third motive that let close because the question is in another language. This is important for us.

2
  • The same problem should occur on any site (different languages though). It's just maybe in the wrong queue.
    – D4RIO
    Sep 3 at 2:02
  • 1
    @D4RIO the queue is not wrong.. is a first time user... the problem is not having one of the highest closing motive (at least on international sites) on the selection.. and the ones there, doesn't cover this particular problem....
    – gbianchi
    Sep 3 at 3:47
9

Honestly not sure if this has been covered already, but it looks like the link to get back to the main Review Queues dashboard has disappeared from the individual queue pages—can we please bring that back, and maybe make it more prominent? Going through the menu is a bit out-of-the-way for me.

9

Selecting "Other Action" in First Questions or First Answers does not clear the post from the queue

I saw that the "Other Action" option was enabled yesterday for both the First Questions and First Answers queues. However, when I select that option, the review is not marked as completed in the post timeline, and it seems that the post stays in the queue till someone chooses one of the other options. Alternatively, there might be a minimum number of "Other Action" reviews expected for it to be cleared, but that has not been documented yet from what I see.

Example of post staying in queue after two "Other Action" reviews:

Two Other Action reviews

Example of post cleared after one "Other Action" and one "Looks OK" review:

One Other Action and one Looks OK review

9
  • @KillingTime Interesting, I went backed and checked my reviews, and I do not observe this. (Example: academia.stackexchange.com/review/first-questions/104707). Perhaps you should add an answer with an example.
    – GoodDeeds
    Sep 9 at 17:23
  • @KillingTime I just realized that you might have meant selecting Edit from the options below the question and closing the review as "Other Action". In that case, yes, the problem persists.
    – GoodDeeds
    Sep 9 at 19:07
  • No, this was using the edit button in the same panel as the "other action", so that it says 'edit' rather than 'reviewed'. Double checking the timeline, this actually created another separate "First Answers" event for the second review so it's a separate bug (which I think has already been reported)...so ignore me, thanks. Sep 9 at 19:35
  • I think any post requires 3 reviewers to be completed regardless of how they action the post. Meaning if the 1st chooses "Looks ok" and a 2nd "Edit" you still need a 3rd reviewer to finish the item.
    – bad_coder
    Sep 13 at 13:53
  • 2
    @bad_coder No, that's not true. Choosing "Looks OK" or "Edit" immediately completes the review. This was also how it was for the First Posts queue. Example: academia.stackexchange.com/review/first-questions/104843
    – GoodDeeds
    Sep 13 at 14:23
  • 1
    @bad_coder Also, it is not just three reviews, here's an example with four: academia.stackexchange.com/review/first-questions/104835
    – GoodDeeds
    Sep 13 at 14:29
  • 1
    This is the most I've seen so far, with 12 and counting: i.stack.imgur.com/x4Zmv.png
    – zcoop98
    Sep 15 at 19:46
  • @zcoop98 Wow...
    – GoodDeeds
    Sep 15 at 19:56
  • 2
    This should be fixed (once it gets live): meta.stackexchange.com/a/369947 Sep 17 at 12:51
8

Per Yaakov's recommendation, I'm posting this as a specific feature-request:

One of the review queue changes I was most excited to see during our research interview was the option to add an "ignored tags" filter... where we could include tags for questions we absolutely did not want to see review items for. However, it seems like it was completely abandoned almost as soon as it was announced. Please re-consider implementing this killer feature to the close & reopen queues.

3
  • 1
    Would you mind posting this as a separate Meta question? Your answer post itself might get lost in the responses here and may not get an accurate picture of how much interest there is for the feature.
    – Lisa Park Staff
    Aug 26 at 16:35
  • 1
    @LisaPark Done
    – TylerH
    Aug 26 at 18:26
  • 1
    Just for my own post-triaging-sake, I'm going to mark this as status-deferred since it has its own post now.
    – kristinalustig StaffMod
    Aug 27 at 12:58
8

Change the text of the "Submit" button to "Continue" if the user chooses a (cancellable) option that has a second step

This is especially useful for the "Share feedback" option (because it opens a modal dialog) but maybe the community should decide if it's a good idea to use it for other options as well (e.g., the "Edit" option).

I think it's more intuitive that way. It will also be in line with my other request about failing audits only at the last step.

1
  • 2
    Yeah, we've gotten this feedback on previous releases as well. We're discussing this today, so we'll have an update on it soon. I agree that this makes more sense.
    – kristinalustig StaffMod
    Aug 31 at 11:52
8

One feature I'm REALLY missing here is the possibility to use a custom comment when leaving feedback.

Sure, I can write a custom comment and then press Looks ok. But that would be wrong. I could write a custom comment, press Edit, make some small changes that are not really changes, and then save. But that would also be wrong.

Well, what I can do, as a really clunky workaround, is that I can choose one of the premade comments. Then I hit back in my webbrowser and click the question or answer I just reviewed. And then I delete the comment I chose earlier and write my own. It's possible, and everything turns out right. But it's a VERY clunky thing to do something that is what I want to do for 99% of the questions I don't seem fit for "Looks good".

5
  • 4
    You are missing the "I'm Done" button for after writing your custom comment.
    – Luuklag
    Aug 31 at 13:05
  • A custom comment? As in posted by Community? :O Aug 31 at 15:05
  • 3
    @Unconsidered No, as in that I choose what feedback to leave on my own instead of choosing between the premade comments.
    – klutt
    Aug 31 at 17:04
  • There's still a "Add a comment", no? Aug 31 at 17:17
  • 7
    @Unconsidered Yes, but as I wrote here, then I'm forced to choose between "Looks's good", "Edit" and "Skip". None of these fit, because I want to leave feedback.
    – klutt
    Aug 31 at 18:11
8

When logged out, review links for First Questions, First Answers, and Late Answers appear completely greyed out. This does not happen for the other queues (for me).

Example from First Questions on Academia SE:

First Questions example, greyed out

On the other hand, an example from the Suggested Edits queue, that appears normal:

Suggested Edits example, normal

6
  • Do you mean links to specific review items? I kind of think they should auto redirect to the main /review page for logged out users. Guests can't review items, and don't really need to know who did what action on a review task anyway.
    – TylerH
    Aug 26 at 18:43
  • @TylerH Yes, I mean links to specific reviews. I have added links to the examples I used, they are accessible without being logged in.
    – GoodDeeds
    Aug 26 at 18:46
  • @TylerH I do not know if links to specific items should be accessible when logged out or not (I am not sure how it was before), but at least the behaviour should be consistent across queues. Also, redirection might make a lot of sense, but I don't see the purpose of greying it out.
    – GoodDeeds
    Aug 26 at 18:47
  • I agree with that (no greying out); I'm just thinking out loud about how it might be best handled moving forward.
    – TylerH
    Aug 26 at 18:53
  • Finally got to this particular bug and am not currently able to repro. Is this still happening?
    – kristinalustig StaffMod
    Sep 15 at 16:00
  • @kristinalustig Yes, looks like it has been fixed.
    – GoodDeeds
    Sep 15 at 18:40
7

Now that "Significant Edits" are firmly a thing, is there any possibility of Allow non-bumping minor edits, but review them on /review becoming a thing? Non-bumping edits would be a very useful thing to have, and it seems as though the "Significant Edit" feature would be the first step towards implementing this.

3
  • 3
    This would have a problem of not alerting the community to potentially problematic edits, and that's why it has never been pursued in the past (the potential for abuse is so high). It would need to be restricted to a higher rep threshold than 2k to be considered, IMO.
    – TylerH
    Aug 26 at 14:15
  • 2
    @TylerH Yes, I'm aware of the potential for abuse if done incorrectly. I'm simply asking if SE would be open to considering the feature request, given that the ability for the feature to be added is now there Aug 26 at 14:20
  • 9
    I think that's a decent idea, but the work to implement that is probably outside the scope of this project. Could you create a separate feature request question for this so that we can track interest and generate further discussion on it?
    – kristinalustig StaffMod
    Aug 26 at 16:12
7

A handful of suggestions for "Share feedback":

Question / answer contains image of code

Please post your code as text, not an image, so others can better understand or reproduce the problem.

Answer is only a link

A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link and quote the most relevant part of the page you're linking to in case the target page is unavailable.

Answer doesn't attempt to answer the question

This does not provide an answer to the question. You can search for similar questions, or refer to the related and linked questions on the right-hand side of the page to find an answer. If you have a related but different question, ask a new question, and include a link to this one to help provide context.

Question / answer contains meta-commentary

This post contains content unnecessary to the post. Please make your posts only about the question you're asking / answer you're proposing.

1
  • Agree with all but the last one, which 1) I don't think is common enough to warrant a canned comment and 2) is generally best fixed by editing out said commentary rather than trying to talk the OP into doing it.
    – Ryan M
    Sep 9 at 10:21
7

First Answers queue - Link to other answers

I have a review where the answer just repeats another answer.

I would like to say this in a comment to the new answer but I can't as there are no share buttons on the Other Answers Page

3
7

This answer describes several issues regarding having the canned feedback appear as a comment from the Community account. Also, this answer asks to allow having those comments be flagged, this one requests being able to undo accidental wrong feedback, and this answer asks for an option to be able to (easily) delete anonymous comments.

In addition, Zanna's comment states:

Please let me (as a mod) delete these comments!

and then further explains in this comment:

Nope! I just get a notification saying the comment will be deleted automatically when the post gets fixed, ...

I don't recall where I read this, but it seems there's doubt about when & how it's determined that the "post gets fixed" so these comments are then deleted. Nonetheless, I believe that at least diamond moderators should be trusted to delete these comments.

The Community bot already does a lot of other things which, in my opinion at least, are not particularly closely related to this new use. I believe creating a new special bot, called something like "Review", to use instead would solve, or at least help mitigate, many of these issues, as well as allow more flexibility in any future added features. These benefits include:

  • The new name would make it clearer to anybody reading the comments where they actually come from. I, even as a relatively knowledgeable user, found it confusing to see comments from the "community" when they are actually from specific users while in the review queue instead. This alternate name should also make it less likely that users think it's from a "moderator", as mentioned in this answer.
  • This should help reduce the chance that people think it's some automatically generated comment, e.g., from a computer algorithm (as explained here), instead of being from a site member during review.
  • The display and behavior can be tailored for the "Review" comments so, for example, they can be modified and deleted by diamond moderators, flagged (as requested here), more easily deleted by regular members (as asked for here), etc.
  • With any other review related features added later that involve using a bot, then having a specific "Review" one available may more easily allow additional customizations and flexibility compared to using the "Community" bot instead.

You must log in to answer this question.

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