https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29346 --- Comment #84 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- (In reply to Nick Clemens from comment #83)
(In reply to Jonathan Druart from comment #82)
There is something wrong with the update_holds_queue_for_biblios task. Try this, in fresh ktd delete itemnumbers 958,960 in a batch and check "delete the biblio if no item remain". You will see 3 update_holds_queue_for_biblios new tasks.
I think we need to revisit this enhancement for the batch tools.
This makes sense, one update each when we remove the items, then a third update when we delete one of the biblios
data: {"biblio_ids":[429],"messages":[{"type":"success","biblio_id":429,"code":"holds_queue_updated"}],"report":{"total_biblios":1,"total_success":1}} data: {"biblio_ids":[430],"messages":[{"code":"holds_queue_updated","biblio_id":430,"type":"success"}],"report":{"total_success":1,"total_biblios":1}} data: {"messages":[{"biblio_id":430,"type":"success","code":"holds_queue_updated"}],"biblio_ids":[430],"report":{"total_biblios":1,"total_success":1}} Yes, it's what it does. But it does not make sense, it's a bug. With 1 batchmod of 2 items, we end up with: 1 task for the main one 3 holds_queue_updated 1 indexing -- You are receiving this mail because: You are watching all bug changes.