commit 6571ca0c2f99ac09d76a1b793af2bc9ae92ceea6 Author: Thibaud Guillot Date: Wed Apr 8 15:28:04 2026 +0200 Bug 6532: Way to move items to another record in batches This patch adds a new "Move items in a batch" feature, allowing to move multiple items from one bibliographic record to another in a single operation. Test plan: 1. Apply the patch and restart_all. 2. Open a record with at least 2 items (record A). Open or create a second record (record B). 3. On record A: Edit -> "Move items in a batch". Select 1 item, enter record B's biblionumber, submit. => Job finishes. The item appears on record B, not on record A. 4. Repeat with "Delete source bibliographic records if no items remain" checked and move the last item of record A. => Job finishes. Record A is deleted. 5. Place a biblio-level hold on a record with 2 items (record C). Go to Edit -> "Move items in a batch". => A warning icon appears on each item explaining that biblio-level holds will follow if no items remain. 6. Move only 1 item of record C to record B. => The biblio-level hold stays on record C (still has 1 item). 7. Move the last item of record C to record B. => Job report warns that the biblio-level hold has been automatically transferred to record B. => Confirm: record B now has the hold, record C has none. 8. You can test also with hold at item level. Hold simply follows the item on the new record linked. 9. Try entering a non-existent biblionumber as destination. => Error shown before the job is enqueued. Sponsored-by: Université Côte d'Azur commit 7b1a348ac9f17c780bd1a5818b1dc0fc760d4b26 Author: Wainui Witika-Park Date: Fri Nov 15 00:57:43 2024 +0000 Bug 38009: Add a generate next button in serials receive page Adds a generate next button to the serials receive page (serials-edit.pl) that works similar to the button on the serials collection page. To test: 1. Go to Staff Client > Serials 2. Find an existing subscription or create a new one 3. Go to the Serials collection page for your serial e.g. /cgi-bin/koha/serials/serials-collection.pl?subscriptionid=1 4. Click on the "Generate next" button and notice that the table adds another row 5. Click on the "Receive" button at the top of the page 6. Notice that the page also shows the issues like the rows in the previous page 7. Apply patch 8. Repeat steps 1-5 9. Notice that the page also has a "Generate next" button at the top 10. Check that the button generates a new issue row on the page Sponsored-by: Pymble Ladies' College Signed-off-by: esther Signed-off-by: Brendan Gallagher Signed-off-by: David Nind Signed-off-by: Laura_Escamilla Signed-off-by: Lucas Gass commit 5e7cb0cf583cd3fd0570b039ab2c6f844b028629 Author: Jan Kissig Date: Tue Apr 28 11:56:32 2026 +0000 Bug 42287: (QA follow-up) Split JS to seperate TT and tidy This splits the script tag in two_factor_auth.tt and member-flags.tt to have a seperate part for interploated TT variables. Signed-off-by: Lucas Gass commit e16a9e92b5748be410ecac07fceb0f96aa40b6d3 Author: Jonathan Druart Date: Fri Apr 3 11:44:23 2026 +0200 Bug 42287: Tidy all script tags - members (auto tidy) Signed-off-by: Paul Derscheid Signed-off-by: Lucas Gass commit 4020a7081904806ad38bea5c78a4b7b3ae71edb2 Author: Jonathan Druart Date: Mon Mar 30 14:17:09 2026 +0200 Bug 42287: Tidy all script tags - members In order to tidy all the script tags of the .tt files we isolate the interpolation of Template::Toolkit variables in a separate script tag. This patch focuses on the members/patrons module. The 2 main changes are in the following files: * moremember.tt => Trivial, simply moving the existing JS variable to a separate script tag * update-child.tt => Trivial, only a single variable created: 'patron_id' Signed-off-by: Paul Derscheid Signed-off-by: Lucas Gass commit af6eca85fb3f87d2d49459ba575b4d8077f42191 Author: Lucas Gass Date: Fri May 8 22:01:42 2026 +0000 Bug 42150: (RM follow-up) Make QA script happy Signed-off-by: Lucas Gass commit 929cb6476363d7356eaf2a96ff9aa207c98f16da Author: Paul Derscheid Date: Fri Mar 27 13:01:02 2026 +0100 Bug 42150: (follow-up) Remove duplicate h export - The explicit `export { h }` from the "Re-export h" follow-up conflicts with `export * from "vue"` added in the "Share Vue via import map" follow-up, since the wildcard re-export already includes h - Remove the redundant named export to fix the rspack build error: "Duplicate export of 'h'" Signed-off-by: Arthur Suzuki Signed-off-by: Thomas Klausner Signed-off-by: Lucas Gass commit afc12b1754974b8a5227439c44604834d0c5fe62 Author: pders01 Date: Sun Mar 22 11:06:26 2026 +0100 Bug 42150: (follow-up) Add nonce to import map script tag The QA test tools require all