Summary: | Changes to Patron's Contact Info Not Logged if Submitted Via OPAC | ||
---|---|---|---|
Product: | Koha | Reporter: | Chris Slone <cslone> |
Component: | Transaction logs | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | lmoran, mkstephens, sally.healey |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Attachments: | Duplication of address on patron modification |
Description
Chris Slone
2017-07-05 15:28:38 UTC
I would like to +1 this. We just had an instance when the changes submitted by the patron in the OPAC and approved in the staff client caused some unintended changes. It was difficult to track down what exactly had happened since there was no log of the request or the change. Created attachment 92389 [details]
Duplication of address on patron modification
I just verified that this bug has been fixed in recent versions, but couldn't pin down the bug report fixing it. |