Bug 32135 - Ability to batch cancel transfers
Summary: Ability to batch cancel transfers
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-08 16:58 UTC by Michael Adamyk
Modified: 2025-07-23 21:41 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Adamyk 2022-11-08 16:58:18 UTC
For consortiums and other large systems, it would be helpful to have the ability to batch cancel transfers, or cancel more than one at a time. 

Most likely the easiest place to do this would be on the Transfers to Receive page, where you might be able to add a "Cancel Transfer" checkbox instead of (or in addition to) the button.
Comment 1 Michael Adamyk 2022-11-08 16:59:43 UTC
Something that would be a super cool addition would be to also have the option to "Cancel and mark lost," but that's probably beyond the scope of a single bug.
Comment 2 Katrin Fischer 2022-11-13 23:06:45 UTC
We now also have transfers to send. Should this be added to both pages?

What's the reason/use case for needing the bulk cancel?
Comment 3 Michael Adamyk 2022-11-14 15:54:56 UTC
Primarily because as a consortium we send a lot of transfers in bulk. There are times when mistakes are made or boxes go missing, and we have to cancel many transfers at once. 

However, it's an inconvenience at worst, so this may be better marked as "Trivial" (if that's that the lowest priority level)?
Comment 4 Katrin Fischer 2022-11-14 16:25:51 UTC
Trivial - blocker are used for errorenous behaviour/problems. I'd say enhancement is right here as it would be a small new feature.
Comment 5 Rebecca Coert 2025-07-23 18:50:45 UTC
(In reply to Katrin Fischer from comment #2)
> We now also have transfers to send. Should this be added to both pages?
> 
> What's the reason/use case for needing the bulk cancel?

One reason would be that sometimes items are withdrawn after being transferred to our processing/cataloging branch. Currently, I have to cancel these transfers one-by-one - which is very time consuming when you have to wait for the "Transfers to Receive" page to reload after every, single cancellation (today was 47 times). It's not a big deal, but it would save A LOT of time!
Comment 6 Rebecca Coert 2025-07-23 21:41:37 UTC
(In reply to Katrin Fischer from comment #2)
> We now also have transfers to send. Should this be added to both pages?
> 
> What's the reason/use case for needing the bulk cancel?

I thought of another reason - Bug 40331 is generating an extra transfer when transfer for hold cancelled due to checkin at incorrect library. I'm currently canceling each of these transfers one at a time. Again, not mission critical, but it takes time to reload the "Transfers to Receive" page over and over.  Thanks for considering!