You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to #93 (Audit Log tab): C7 EE Cockpit additionally allows setting and clearing an annotation on user operation log entries. The read-only Audit Log tab proposed in #93 displays the annotation column but offers no way to edit it.
Expected (C7 EE Cockpit parity)
Each audit log entry offers an "edit annotation" action; saving calls
PUT /history/user-operation/{operationId}/set-annotation { "annotation": "..." }
PUT /history/user-operation/{operationId}/clear-annotation
(both community REST endpoints), then reloads the log.
Suggested implementation
Two new functions in src/api/resources/history.js (set_user_operation_annotation, clear_user_operation_annotation).
Note: an operation id groups multiple log entries (one per changed property); the annotation applies to the whole operation — the UI should edit per operationId, not per table row.
Summary
Follow-up to #93 (Audit Log tab): C7 EE Cockpit additionally allows setting and clearing an annotation on user operation log entries. The read-only Audit Log tab proposed in #93 displays the annotation column but offers no way to edit it.
Expected (C7 EE Cockpit parity)
Each audit log entry offers an "edit annotation" action; saving calls
(both community REST endpoints), then reloads the log.
Suggested implementation
src/api/resources/history.js(set_user_operation_annotation,clear_user_operation_annotation).operationId, not per table row.