Follow-up from Issue #8:
(Some of?) the error messages presented to users are rather cryptic/off point, and the app can get to plain HTTP 500 when parsing "incorrect" data.
It might be worth reworking the error messages/app flow so it provides more helpful information.
Metadata Update from @jskladan: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/testdays-web/issues/9
Please continue any further discussion there.
Log in to comment on this ticket.