maziggy ad3b295312 fix(archives): let Items Printed go to 0 for a ruined plate (issue #3051) ...

A jam can destroy everything on the plate while the printer still reports the
    job as a success, so the honest count of usable parts is zero. The edit dialog
    floored the field at one, and a project's completed-items count sums that
    column, so there was no way to record that a job produced nothing.

    The floor was in the dialog only; the API stored whatever it was given, which
    also meant a negative count was accepted and would have subtracted from the
    project totals. The column is now bounded at zero instead.

    Filament Trends counted prints as `quantity || 1`, which would have read a
    deliberate 0 as "unset" and charged the ruined plate as one print while the
    project page counted none.

2026-09-20 13:33:46 +02:00

..

app

fix(archives): let Items Printed go to 0 for a ruined plate (issue #3051)

2026-09-20 13:33:46 +02:00

tests

fix(archives): let Items Printed go to 0 for a ruined plate (issue #3051)

2026-09-18 13:07:00 +02:00

__init__.py

…