Summary: | Ability to batch cancel transfers | ||
---|---|---|---|
Product: | Koha | Reporter: | Michael Adamyk <madamyk> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, kyle, rcoert |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Michael Adamyk
2022-11-08 16:58:18 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. 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? 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)? Trivial - blocker are used for errorenous behaviour/problems. I'd say enhancement is right here as it would be a small new feature. (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! (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! |