Bug 33508 - Submitting patron update request from OPAC deletes any pending updates
Summary: Submitting patron update request from OPAC deletes any pending updates
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-12 16:33 UTC by Donna
Modified: 2023-06-22 12:07 UTC (History)
3 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Donna 2023-04-12 16:33:36 UTC
When a patron submits a request for update of their personal information, if they submit another request before the first one is approved, the info is deleted.

To demonstrate:
1.  In OPAC, submit a update changing street address (or any field)
2.  View in staff interface and see that the submission shows. Do not take any action on it.
3.  Go back to OPAC and submit an update for something else, such as phone number
4.  In staff interface, view the new update request and see that only the last one (phone number) shows, the address request has been removed.

This is a problem because patrons have no indication that their previous request is being deleted, and staff have no idea that other updates have been requested.  For instance, a patron goes into their account and updates address, then realizes they also need to change phone number, and there is no way for them to know they are deleting the previous request.

We need to either block patrons from being able to overwrite the previous request, or find a way to retain both requests. I think the second option would be the most customer friendly.
Comment 1 Sally 2023-06-22 12:07:34 UTC
This is one of those silent bugs - where unless a patron complains, you'd never know it was happening.

It's on master and goes back to at least 20.11.  

Consolidating all updates would be great, but I guess that might be trickier.

In the meantime, blocking the patron from making further changes would be a useful solution - especially if there was an information message warning that they can't make any changes as they already have changes pending approval.

I've changed the bug status to normal rather than enhancement, due to the potential for data loss.