Internal messages between different states.

Moving to the workbench moderation issue queue.

Isn't the 'Revision information' textarea already used for this?

From the usability point of view, a comment field would be a great improvement. At present, when an editor rejects a node, there is no text box for a comment explaining why the node is being rejected. The editor simply clicks on the Draft link in the Moderate column of his Needs Review screen. The contributor now sees the node as a draft, but with no explanation as to why it was rejected. Result: an annoyed and frustrated contributor!

The editor could click on the node name in his Needs Review screen and open up the article. Click on the Edit Draft tab and then Publishing Options. Change the review state to draft and add an explanation in the Moderation Notes textarea. The contributor now sees the explanation on the Moderate screen for that article - it's below the node name in the title column - but this creates a new revision of the node.

One solution might be to add a Workflow Status column in the contributor's 'Content I've Edited' table which would include any comment that accompanied the last state change.

@Dave Reid -- the revision log field doesn't work for this, since moderating content doesn't create a new revision.

There's been discussion around making moderation records fieldable entities, which would provide the opportunity for a 'moderation notes' field.

+1 for the comment field

We're currently working on a pitch presentation and trying to meet the client's requirement that moderation comments be possible. I think that's what many editorial staff will appreciate.

The work here will make this possible: #1294880: Convert Workbench Moderation records to entities

Please test that branch to help move this forward.

So we are exactly 2 years later now :)

I really love workbench moderation and i'm thankful for all your work.
But how should we implement this request?

Since this issue hasn't seen any action (and the linked issue got punted over to state machine for the 2.x branch), there is an additional contrib module that does this for workbench mdoeration 1.x: https://drupal.org/project/workbench_moderation_notes

It strikes me though that this module would be better served as a patch to workbench moderation since it overwrites (and copies) some of the functionality from workbench moderation to do it's thing. I'm going to re-open this issue and potentially work on a patch for this.

If the https://drupal.org/project/workbench_moderation_notes module is going to be merged in workbench_moderation (which is a great idea by the way!), please also take a look at https://drupal.org/node/2253981.
I've added a patch that solved some of the transitions not having a log message. Hope it helps!