What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

When the Community user rejects an edit during the grace period there is no obvious reason visible (example).

Community♦ reviewed this 1 hour ago: Reject

This causes some confusion for the user who suggested the edit. See also:

I’m afraid these “rejects without a reason” are not helpful and rather discouraging. A short explanation would be useful, and the suggester could learn something.

share|improve this question
14  
Yes, I would love to be able to type: "did not fix every problem with post" or "randomly highlighting words is not considered a 'good' edit" –  ben is uǝq backwards Nov 2 '12 at 13:25
    
Supporting this feature-request - happened to me as well –  Philipp M Oct 1 '13 at 9:34
    
Future viewers, if confused, might be interested in "Why does the Community user approve and reject edits?" –  Emrakul Feb 21 at 6:59

6 Answers 6

up vote 15 down vote accepted

Kevin whipped this up a couple of days ago. You can view an example here:

Conflicted with a subsequent edit.

These rejections do not count toward edit bans or warnings.

share|improve this answer
2  
Oh, wow, I didn’t expect an answer anymore. :) Looks good. –  toscho Aug 21 at 20:26
    
is this already deployed? I ask because there is a complaint at TWP meta that seems to suggest that 6 hours ago there still was an issue and the edit complained about doesn't show "Conflicted..." message: workplace.stackexchange.com/review/suggested-edits/20238 –  gnat Aug 22 at 13:42
1  
@gnat most likely it's only on Stack Overflow where most conflicts happen. –  Shadow Wizard Aug 22 at 20:42
1  
It is now, @gnat: workplace.stackexchange.com/review/suggested-edits/20277 - not sure what happened there. –  Shogging through the snow Aug 22 at 21:33
    
thanks! –  gnat Aug 22 at 21:36
    
Its good to know these rejections don't count toward bans, but still very discouraging to see my accept/reject ratio affected by this. Under these circumstances I wish I'd never attempted the edit at all - its too bad the count doesn't work that way too. –  trooper Dec 17 at 2:10

It's more than just discouraging, each rejection has impact on the user suggesting the edit as it might lead to a ban.
The above is no longer true, as of June 4th 2013:

We now completely ignore any suggested edits that were rejected by the Community User when determining whether someone be banned from reviewing suggested edits

This is a blessed change, however it's also worth to note that the Community user is rejecting lots of suggested edits, and it looks like it's on a drastic rise. For example on September 18th 2012 it rejected 59 suggested edit while on April 11th 2013 it rejected 112 suggested edit. (Just two random dates)

I agree that those poor souls deserve to know the reason why their edit got rejected, same way that flesh and blood users can choose or write a reason.

Taking a sample case, here is a mockup that will save some tears and frustration:

share|improve this answer

This happened to me today here. The edit that I suggested came 13 minutes after the question was posted so it wasn't that the question was edited within the grace period.

Also, there is no evidence to support that a reviewer improved on the post by further editing it and marking my edit as unhelpful. The post was edited by another user at a later stage but I believe this to be unrelated.

If a reject reason was added as suggested here, it would make the process much more user friendly and potentially reduce the number of new questions being opened requesting clarification for the reject reason.

As noted by Sha Wiz Dow Ard, the community user is rejecting quite a few suggested edits lately (examples from same user 1, 2). Perhaps there is some issue with it? If this behaviour continues, it will likely put people off suggesting edits and that would be a shame seeing as they are trying to improve on the quality of the content on the site.

share|improve this answer

As I had this happen to me today (on WPSE), I was unsure of whether there was an inherent problem with the edit or not - obviously not.

This should be mandatory as the user being rejected might actually consider the edit to have been rejected by a real reviewer and as you suggest, with no explanation, that's discouraging.

Top suggestion.

share|improve this answer

Going to completely support this one.

A user posted a question with some unrelated tags (presumably for the purpose of making the question more visible), so I suggested an edit removing all the superfluous ones. Two real people quickly approved, and then I saw it was rejected by Community. No explanation, basically just a f**k you. This pretty much sends the message that I should stop bothering to make edits (at least until I have enough rep that I don't need them approved) - especially considering this isn't the first time one of my edits has been approved by two real people (other times more substantial than just a re-tag) and then shot down by the Community bot.

share|improve this answer

Wholeheartedly agree with this one, it happened to be only a couple of hours ago again, it's disheartening to know that you're trying to make the question / answer better, and it gets shut down with no explanation, there's only really ever 2 possible scenarios:

  1. The person disagrees with your change
  2. The edit submitted was actually wrong

Either way, it makes sense that a reason be given, even if it's chosen from a preselected few options like when you are flagging an item, that way that editor can know the reason for the rejection (heaven forbid, even learn form it themselves)

share|improve this answer

You must log in to answer this question.

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