Confirmed in the 3.3.2 web client. I'm seeing the same errors in osrfsys.log after checking in an item that triggers a transit, and then trying to mark it damaged. No error is given to the user.
Confirmed in the 3.3.2 web client. I'm seeing the same errors in osrfsys.log after checking in an item that triggers a transit, and then trying to mark it damaged. No error is given to the user.