https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31031
Jason Robb <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Jason Robb <[email protected]> --- Our workflow involves marking items "Long overdue (lost)" with the cron, but leaving the item checked out so staff can evaluate and make the final call on charging the item to the account by then marking it "Lost and charged". We typically do this from the items tab which is a single step. Using batch item modification, it requires the removal of the first lost status in one job, then the application of the new lost status in a second job to force the charge/checkin action. If it can work in one step in one place, it makes a two-step process in other places seem clunky. It'd be awesome if instead of tying how this works to what page you're on, it is tied to what status you are applying. Bug #22780 touches on that idea. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
