Under Community Review

Thanks for the idea.

We've seen similar functionality created as an extension, for example, that adds a "Save & Comment" feature. However, the extension does not use the standard commenting field.

As a follow-up to the community, who would typically be expected or able to create or adjust a comment? Would anyone be able to change a Comment or certain people?

Does it matter if these notes are in the current Comment field? Would a separate, possibly new field, be just as useful?

Finally, would a change to a comment count as a change to the item's version? For example, if a user could change the comment on item version 2.0, would this remain the same item at version 2.0, or might this count as a change to the item?

Allow to edit "comments" in the History view of elements

Sometimes is needed to mark a certain version to be able to be referenced, but we only have the standard comments in the history list.

So the ability to edit this comments could be very usefull, for example in Continuous Integration activities

Raul Escudero

  • Who would typically be expected or able to create or adjust a comment:

    - create, anyone (their name/id is noted).

    - update, admin (or a more granular 'chief-editor')

    In the current Comment field?

    - We've worked with various extensions and usually at the request of auditors - so long as they can be accessed (and even better exported) I don't think it would be super-important IMHO

    Change to a comment count as a change to the item's version?

    - No. this could suggest workflow requirements etc. The comment is auditing, not "content" - which is why 'editing' comments would be something to consider very carefully if even allowed.

    Would be great if this included when *un*localising an item (or even localising) :)