Bug 14104 - Renew check-box appears on checked out items with item level holds
Summary: Renew check-box appears on checked out items with item level holds
Status: RESOLVED DUPLICATE of bug 13919
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-30 21:47 UTC by Barton Chittenden
Modified: 2015-05-15 06:30 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barton Chittenden 2015-04-30 21:47:28 UTC
As of 3.18, it is possible to renew an item that has a hold on it, as long as the hold can be filled.

If a biblio-level hold is placed, and all items are checked out, the 'Renew' check-box in the 'Checked out' tab in circ/circulation.pl will be replaced by the text 'On Hold'.

If the checked out item has an item level hold on it, the 'Renew' check box *will* show, and no 'On Hold' text will display.

If you select the 'Renew' check box for that item and click "Renew or check in selected items", the renew *will* fail, and the check box will then be replaced with the message 'Renew failed: on reserve'

The issue not that the item is renewable, but simply that we are not being consistent about how we display the renew-ability of the item.


1) log in to http://intranet.bywatersolutions.com/ (user: bywater pass:bywater)
2) Check out item The Avengers 0003039002483 to Bilbo Bagins (55)
3) In separate tab, place Item level hold on The Avengers 0003039002483
4) Display check outs -- The Avengers 0003039002483 *does* show as renewable (i.e. the check box is available, and the 'on hold' text does not show)
Comment 1 Katrin Fischer 2015-05-15 06:30:43 UTC

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