When batch deleting patrons from a patron list, and the list includes staff patrons, it doesn't let you delete the staff patrons in the list. To replicate: 1. Create a patron list (Tools > Patrons and circulation > Patron lists > + New patron list). 2. Add two patrons to the list, with one of them a staff patron (such as Henry): 2.1 Enter at least three characters in the patron search field and select a patron (examples: hen, mar) 2.2 Repeat until you have two patrons that are listed under the 'Patrons to be added' heading 2.3 Select 'Add patrons' to add to the list 3. Go back to the patron lists (Tools > Patron lists). 4. For the list you created, select Actions > Batch delete patrons. 5. Note that the warning message - the count is wrong (should be 2 patrons will be deleted): Warning 1 patrons will be deleted 0 patrons' checkout histories will be anonymized 6. Repeat steps 1-5 where the patrons in the list are not staff patrons. The count of patrons to delete should equal the number of patrons in the list. Other notes: 1. I added patrons from all patron category types to the patron list (where there are patrons in that category). 2. I also checked the staff patron information, and they weren't protected. 3. I testing using koha-testing-docker and was logged in as the koha user. 4. I couldn't see any options in the patron category form that would prevent deletion. I'm not sure if I am right that you can't delete staff patrons this way - there may be another reason why this is happening.
I believe this is an intended feature. You never could delete patrons with a patron category that has the category type "staff" with the batch anonymization tool. The problem here might be a lack of feedback? I think I have seen another bug that was about the lack of good feedback on the reasons why a patron could not be deleted, but not spotting it right now.
(In reply to Katrin Fischer from comment #1) > I believe this is an intended feature. You never could delete patrons with a > patron category that has the category type "staff" with the batch > anonymization tool. The problem here might be a lack of feedback? > > I think I have seen another bug that was about the lack of good feedback on > the reasons why a patron could not be deleted, but not spotting it right now. Thanks Katrin! I think that is bug 24483. I've marked this one as a duplicate... *** This bug has been marked as a duplicate of bug 24483 ***