Bug 34159 - comments and history for UDM objects
comments and history for UDM objects
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 4.2
All Linux
: P4 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
Depends on: 11151
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-19 17:34 CET by Ingo Steuwer
Modified: 2020-07-03 20:51 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2013111121002796
Bug group (optional): Roadmap discussion (moved)
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Steuwer univentionstaff 2014-02-19 17:34:36 CET
In many situations a change-history for UDM objects would be helpfull. We should add

1. a history of changes per object (user, timestamp, changed attributes, optional comment), including the possibility to be generated by UDM automatically

2. allow to generate those history manually
Comment 1 Ingo Steuwer univentionstaff 2014-06-12 10:08:44 CEST
see also Bug #25907

history in LDAP requested by 2013111121002796
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:35:39 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Florian Best univentionstaff 2019-03-09 23:29:18 CET
First approach for this is the admin diary. WORKSFORME?
The admin diary only logs if objects were changed, not which attributes.
Comment 4 Ingo Steuwer univentionstaff 2020-07-03 20:51:04 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.