On Beta sites, you get the Close/Reopen privilege at 500 reputation, before the Edit privilege (1000 reputation). This means that the Edit button, which is normally visible in the Close Votes review queue on designed sites (where the closing privilege is earned after the editing privilege):

"Close Votes" review queue button selection on a site where the user has both closure and edit privileges; in order, the buttons are "Leave Open", "Close", "Edit", and "Skip"

...is hidden on beta and non-designed sites:

"Close Votes" review queue button selection on a site where the user has closure but not edit privileges; in order, the buttons are "Leave Open", "Close", and "Skip"

...if the user has enough rep to vote to close, but not enough to edit.

However, in the Reopen Votes review queue, there is an Edit option:

"Reopen Votes" review queue button selection on a site where the user has closure but not edit privileges; in order, the buttons are "Leave Closed", "Edit and Reopen", "Reopen", and "Skip"

Since it's just as important to edit a question to save it from being closed, as it is to edit it to get it reopened, can we enable the Edit button in the Close Votes review queue as well, even if the reviewer doesn't have editing privileges?

  • Can anyone provide history or an explanation as to why the order of those privileges is different for beta sites? It's not intuitive to me.
    – Will
    Sep 26, 2018 at 13:12
  • 1
    @WillCain Sonic just posted a question about that.
    – Glorfindel Mod
    Sep 26, 2018 at 13:12
  • What does "…designed…" and "…non-designed sites:…" mean? I realize this was added by a different user but maybe you understand? I would place the screen images in block quotes, it would look less confusing. Sep 26, 2018 at 16:56
  • Sites which have graduated but did not receive a custom design yet. Examples: Code Golf, Philosophy, Anime & Manga.
    – Glorfindel Mod
    Sep 26, 2018 at 17:00
  • ^ those are non-designed, non-beta sites. They still have the privilege levels of a beta site.
    – Glorfindel Mod
    Sep 26, 2018 at 17:06
  • 2
    Folks, please don't remove tags just for the sake of making room for a status tag, we'll do that when (or if) we add one. Thanks!
    – user50049
    Nov 1, 2018 at 16:02
  • While I understand wanting to have parity with the non-beta sites, the "Edit" button in review queues, as a review response, is broken. Primarily it's used to fix trivial formatting issues with the post. While fixing such things is normally good, the bad thing is that an "Edit" response in a review queue removes the post from the review queue. IME, it's very rare for the edits performed there to actually resolve the underlying problems with the post (i.e. the post should not be kicked out of the queue). If just the normal post "edit" button was enabled, that would be good.
    – Makyen
    Aug 5, 2020 at 23:30
  • I've thought about this for a while, and this may not make sense as written. The Edit action, as @Makyen pointed out, counts as a binding Leave Open review, and if this is implemented as written, this would allow the task to be completed just by submitting a suggested edit. What if said suggested edit is rejected, though? The question will still (probably) be in a closeable state. I think the best thing is to not have edit suggestions count as a binding Leave Open review, but as a single such review, or not count toward that count. Nov 11, 2020 at 2:53

2 Answers 2


Going forward, all users who can participate in the Close Votes queue will see an Edit action on the tasks. Users with full edit rights will be able to make the edits just as before, while users who are only able to suggest edits will be submitting suggested edits instead.

As part of this change, we are also starting to count "Edit" reviews the same way we count "Leave open" ones: each Close Votes review task will need to reach the required review threshold with a combination of "Edit" and "Leave open" reviews. (The old behavior was that only "Leave open" reviews counted towards that threshold, but "Edit" reviews resolved the task immediately.)


We are in the middle of a project to update our Review Queues and will dive deeper into this request as part of this project. Can't guarantee that we will implement this particular suggestion, but we will absolutely consider it and update this ticket when we are further along.

You must log in to answer this question.

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