Bug 26643

Summary: Staff should be notified that a transfer has been completed on checkin
Product: Koha Reporter: Martin Renvoize (ashimema) <martin.renvoize>
Component: CirculationAssignee: Martin Renvoize (ashimema) <martin.renvoize>
Status: CLOSED FIXED QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: b.pastern4k, gmcharlt, hblancoca, jonathan.druart, josef.moravec, kyle.m.hall, lucas, oleonard, sally.healey
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25377
Change sponsored?: --- Patch complexity: Trivial patch
Documentation contact: Documentation submission:
Text to go in the release notes:
This patch introduces a notification message on the check-in screen to highlight when the check-in has resulted in the completion of a transfer.
Version(s) released in:
20.11.00
Circulation function:
Bug Depends on: 22164    
Bug Blocks: 22160    
Attachments: Bug 26643: Notify librarian of completed transfers
Bug 26643: Notify librarian of completed transfers
Bug 26643: Notify librarian of completed transfers
Bug 26643: (QA follow-up) Fix typo in message

Description Martin Renvoize (ashimema) 2020-10-09 12:15:30 UTC
It was brought to my attention, on bug 25377, that some users were unaware that the action of checking in an item at a branch can trigger the completion of a transfer.

We should notify the user that a transfer has been completed to clarify that this action has taken place.
Comment 1 Martin Renvoize (ashimema) 2020-10-09 12:16:10 UTC
Created attachment 111397 [details] [review]
Bug 26643: Notify librarian of completed transfers

It came to light that it's not clear to all users that a checkin results
in the completion of a transfer if one exists for the item being checked
in.  This patch adds such a notification to the error messages loop to
highlight that the item has been recieved from it's sending brnach.

To test
1/ Setup a transfer from branch A to branch B
2/ Check the item in at branch B
3/ Note that a new message appears in the 'Check in message' alert box
saying "Item recieved from branch A"
4/ Signoff
Comment 2 ByWater Sandboxes 2020-10-09 14:14:39 UTC
Created attachment 111404 [details] [review]
Bug 26643: Notify librarian of completed transfers

It came to light that it's not clear to all users that a checkin results
in the completion of a transfer if one exists for the item being checked
in.  This patch adds such a notification to the error messages loop to
highlight that the item has been recieved from it's sending brnach.

To test
1/ Setup a transfer from branch A to branch B
2/ Check the item in at branch B
3/ Note that a new message appears in the 'Check in message' alert box
saying "Item recieved from branch A"
4/ Signoff

Signed-off-by: Sally <sally.healey@cheshiresharedservices.gov.uk>
Comment 3 Katrin Fischer 2020-10-14 12:15:47 UTC
Created attachment 111607 [details] [review]
Bug 26643: Notify librarian of completed transfers

It came to light that it's not clear to all users that a checkin results
in the completion of a transfer if one exists for the item being checked
in.  This patch adds such a notification to the error messages loop to
highlight that the item has been recieved from it's sending brnach.

To test
1/ Setup a transfer from branch A to branch B
2/ Check the item in at branch B
3/ Note that a new message appears in the 'Check in message' alert box
saying "Item recieved from branch A"
4/ Signoff

Signed-off-by: Sally <sally.healey@cheshiresharedservices.gov.uk>

Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Comment 4 Katrin Fischer 2020-10-14 12:15:54 UTC
Created attachment 111608 [details] [review]
Bug 26643: (QA follow-up) Fix typo in message

Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Comment 5 Jonathan Druart 2020-10-15 10:55:50 UTC
Pushed to master for 20.11, thanks to everybody involved!
Comment 6 Lucas Gass (lukeg) 2020-11-13 15:38:09 UTC
enhancement will not be backported to 20.05.x
Comment 7 Martin Renvoize (ashimema) 2021-03-15 15:27:49 UTC
*** Bug 22164 has been marked as a duplicate of this bug. ***