Bug 36848

Summary: Cannot make "Protected" field required via BorrowerMandatory syspref
Product: Koha Reporter: Lucas Gass (lukeg) <lucas>
Component: PatronsAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: dcook, emmi.takkinen, gmcharlt, kyle.m.hall
Version: Main   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Lucas Gass (lukeg) 2024-05-13 22:40:43 UTC

    
Comment 1 Emmi Takkinen 2024-05-29 06:26:11 UTC
I was actually considering to fix this while working on bug 36825. But then I thought that isn't this unnecessary? Unlike input fields or sometimes select fields, "Protected" field always defaults to "No" since it's coded to be that way. So it's never "empty" and IMO there really is no need to make it mandatory.
Comment 2 David Cook 2024-05-29 06:58:14 UTC
Yeah that's a good point. If we had different mandatory profiles for different categories, then it would be useful, as you could force staff users to be protected for instance.

But I can't think of a scenario in current Koha where this would actually work as intended. You'd just end up making everyone protected by accident...