I'm really not sure what the best solution is here - opinions? http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9322 I think we do not want to lose any data regarding transfers, no matter how weird or nonsensical an action might be, a librarian might legitimately want to do chained transfers, so we should not disallow that. A librarian might also legitimately want to have a transfer and a reserve going at the same time and choose between them at check-in time. So what is the best way to fix this problem of multiple transfers from multiple sources (branchtransfers and reserves transfers being the different origins of transfers) being all cancelled when one is completed? The current behaviour is blocking other very useful (and paid for) development - and the bug itself causes librarians discomfort quite often in the form of "lost and stuck reserves." Thanks for your time and thought, Liz