Bug 14798 - Renew and checkin do not update parts of checkout page
Summary: Renew and checkin do not update parts of checkout page
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: All All
: P5 - low minor (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
: 14947 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-09-09 17:07 UTC by Agnes Rivers-Moore
Modified: 2020-01-08 07:17 UTC (History)
7 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 Agnes Rivers-Moore 2015-09-09 17:07:34 UTC
When the checkout table is updated by renewing or checking in a selected item, the page does not refresh. 
This leaves the message "Patron has ITEMS OVERDUE" in red at the top right of the screen when actually no items are overdue.
If the item is checked in, it leave the item visible in the Checked Out items table - with the message "checked in"

Some of this may be an intended feature, so - comments welcome!

My request is that a modification is made so that at least the ITEMS OVERDUE message is removed once the renewals are completed.
I think in earlier versions the whole page was refreshed - checked in items disappeared, and the Items Overdue message disappeared once the "Renew or check in selected items" button was clicked.
Now that the table is Ajaxed, simply refreshing the entire page might have possible unforeseen consequences that developers may need to address.

Note that you can see this effect also - if a barcode is typed into the "Enter item barcode" box, but check out is not completed, and then you renew or check-in an item in the checkout table, the barcode remains in the box.
Comment 1 Liz Rea 2015-10-02 02:36:38 UTC
This should be fixed along with Bug 14803
Comment 2 Katrin Fischer 2020-01-08 07:17:32 UTC
*** Bug 14947 has been marked as a duplicate of this bug. ***