Prevent re-queueing a tournament match that’s already in database #813
Labels
module: backend
Related to the Siarnaq backend module
priority: p1 critical
type: feature
New feature or request, or quick non-essential bugfix
(regardless of its state,, including even if the match is errored)
If users want to do this, they should instead rescind the match from the tournament state (see #812), and then re-create this match. This protects tournament state
The text was updated successfully, but these errors were encountered: