https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19814

--- Comment #114 from Marcel de Rooy <[email protected]> ---
(In reply to Martin Renvoize (ashimema) from comment #113)
> That really had me scratching me head.. I think some of it was for audit
> reasons and is pre-existing functionality.. the other bit I've fixed with a
> follow-up and is about ModReserve mis-identifying some transfers and marking
> them complete when really it shouldn't.

Thx for doing so.
I retested step 5 now.

After that branchtransfers looks like:
|               141 |          4 | 2026-08-21 10:35:54 | 2026-08-21 10:35:54 |
CPL        | NULL        | 2026-08-21 10:37:14 | FFL      | BATCHTEST19814 |
Manual       | WrongTransfer       |
|               142 |          4 | 2026-08-21 10:37:14 | NULL                |
CPL        | NULL        | NULL                | FFL      | NULL           |
Manual       | NULL                |
|               143 |          4 | 2026-08-21 10:37:14 | 2026-08-21 10:37:14 |
CPL        | NULL        | NULL                | MPL      | NULL           |
Reserve      | NULL                |
|               144 |          8 | 2026-08-21 10:37:15 | 2026-08-21 10:37:15 |
CPL        | NULL        | NULL                | MPL      | NULL           |
ReturnToHome | NULL                |

The transfer to FFL is cancelled as we expect. The Reserve transfer from CPL to
MPL arrived as expected.
But unfortunately, I still see a new manual transfer from CPL to FFL. Not sent,
only requested. Should we really create that one? I am not sure.

The two follow-ups look good to me btw. Maybe we should just leave this as-is
now, since it feels like we want to fix existing 'bugs' that go out of scope?

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to