The transfers system is very much tied to the Holds/Reserves features at the moment, but slowly some other subsystems are starting to use it too (Stock Rotation, Rotating Collections). For full audit purposes, we should record what triggered the transfer. Currently stock rotation misuses 'comments' to record the 'trigger' and these comments can be obliterated by subsequently triggered transfers.
Created attachment 96594 [details] [review] Bug 24287: Add `trigger` to `branchtransfers` This patch adds the `trigger` field to the `branchtransfers` table to record what triggered a transfer.
Created attachment 97501 [details] [review] Bug 24287: Add `trigger` to `branchtransfers` This patch adds the `trigger` field to the `branchtransfers` table to record what triggered a transfer.
Test plan: Apply patch, run updatedatabase. Varify the new 'trigger' field is added to the database. (Bonus points, check that a fresh install does the same)
Created attachment 97516 [details] [review] Bug 24287: Add `trigger` to `branchtransfers` This patch adds the `trigger` field to the `branchtransfers` table to record what triggered a transfer. Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Created attachment 97532 [details] [review] Bug 24287: Add `trigger` to `branchtransfers` This patch adds the `trigger` field to the `branchtransfers` table to record what triggered a transfer. Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Created attachment 98023 [details] [review] Bug 24287: Add `reason` to `branchtransfers` This patch adds the `reason` field to the `branchtransfers` table to record what triggered a transfer. Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Nice work everyone! Pushed to master for 20.05
enhancement not backported to 19.11.x