Open benoit74 opened 11 months ago
Duplicate of #740
This is not really a duplicate, I was only speaking about duplicated names. Not about duplicated configuration as in #740. This issue is probably way easier to solve than #740 and would avoid 500 errors
Problem
When cloning a schedule, if the new chosen name is already in used, this is only detected at the DB level, raising a 500 error.
We should detect this at least at the API level, and maybe also at the UI level (effort to be investigated).
Reproducing steps
Clone a schedule and choose a name which is already in use.