Bug 17217

Summary: Allow to reserve first available item from a group of titles (OPAC)
Product: Koha Reporter: Julian Maurice <julian.maurice>
Component: Hold requestsAssignee: Julian Maurice <julian.maurice>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: dcook, gmcharlt, nicolas.legrand
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Bug Depends on: 15516    
Bug Blocks:    
Attachments: Bug 17217: Allow to reserve first available item from a group of titles (OPAC)

Description Julian Maurice 2016-08-29 13:27:03 UTC
This bug follows bug 15516.

This is the OPAC part
Comment 1 Julian Maurice 2016-08-29 13:34:08 UTC
Created attachment 54978 [details] [review]
Bug 17217: Allow to reserve first available item from a group of titles (OPAC)

Depends on bug 15516

Test plan:
0. Run updatedatabase.pl and misc/devel/update_dbix_class_files.pl
1. Go to OPAC search, display some results, click on some checkboxes and
   click on 'Place hold' button at the top of the results
2. Check the box with label "Place a hold on the first available..."
3. Check that more options appear (Pickup location, hold dates and
   notes).
4. Click on 'Place hold'
5. Now go to intranet interface and check in an item of one of the
   reserved biblios and confirm the hold
6. The hold status should have been changed to Waiting, and all other
   holds should have been deleted
Comment 2 Nicolas Legrand 2016-10-13 12:33:28 UTC
- on opac-reserve.pl you should consider changes in Bug 15516 and change AddReserveGroup() to AddHoldGroup()

- when at 3. I don't see notes field

- when checking in an item, clicking on "confirm hold" or "print and confirm" do the job, but send me to a 500 error

- everything else working as it should
Comment 3 Owen Leonard 2017-04-10 18:15:19 UTC
Based on comment 2 I think this should be 'Failed QA'
Comment 4 David Cook 2021-07-08 04:56:16 UTC
I'm marking this as a duplicate because this functionality is actually provided by bug 15516 these days

*** This bug has been marked as a duplicate of bug 15516 ***