Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Paweł Albecki
Paweł Albecki(Deactivated)Reporter
Mary Jo Kochendorfer
Mary Jo Kochendorfer(Deactivated)Story Points
5
Original estimate
1w
Time tracking
2d 5h 30m logged2d 2h 30m remaining
Components
Sprint
None
Fix versions
Priority
Time Assistant
Time Assistant
Created April 18, 2017 at 9:33 PM
Updated May 24, 2017 at 11:01 AM
Resolved May 22, 2017 at 5:51 AM
When details of a user are updated/modified the system should log the change, date and user that made the change. This should happen for any field in the user object. Similar to the pattern outlined for facilities here.
Javers is currently enabled in the service, available for audit logging of entities. Turn on audit logging for the User entity by attaching Javers annotations to the entity class and its corresponding repository class.
Scope In:
modifications to user details (name, email, etc.)
Modifications to home facility
loginRestricted
timezone
Scope out:
this does not include the ability to view the audit log table through the UI
does not include the associations between users and roles.
Acceptance Criteria
Every change made in the UI or by upload to the User object (see Scope In) is logged in the system
Each change should be tracked and tied to a date/user that made the change
Provide a basic API endpoint to see the full audit log for a specific user (/api/users/<id>/auditLog); see /api/facilities/<id>/auditLog for a pattern
Background : https://openlmis.atlassian.net/wiki/display/OP/Audit+Logging+of+State+Changes
Admin can create and edit all user details (Username, email, firstname, lastname, loginrestricted)
Admin can add and remove Home Facility (affects Supervision role program assignments)
Looking forward, need to create another ticket for role assignment