Describe the bug
Setting a child session to start after a parent session has ended (via the session schedule options) results in an error but the option still seems to apply (waiting to test if the session will actually start after the parent session though). Also unable to disable option anymore via "Remove schedule", instead having to click "Schedule" to save the option being unticked, which then schedules the session for the default date and time already entered, resulting in a further step to then remove that unwanted scheduling.
These issues only started occurring after patch v2.1.3 was applied, previous to that no error occurred and the option could be disabled via "Remove schedule".
To Reproduce
Error
Create/edit a championship race weekend.
Click "Schedule session" on a child session, tick "Start after Parent Session has completed" and then "Schedule" to apply.
Cancelling
Click "Schedule session" on a child session already set to start after a parent session.
Click "Remove schedule" - See that the option remains ticked after refreshing the page.
Untick "Start after Parent Session has completed" and then "Schedule" to apply the change.
Go back in and click "Remove schedule" to remove unwanted date and time scheduling applied as a result of step 3.
Expected behavior
Enable child sessions to start when parent sessions have finished irrespective of date and time prefilled into schedule session popup and disable when needed.
Screenshots
Error after configuring a session to start after parent session (happens irrespective of prefilled date and time or setting a different future date and time to try and avoid the error due to what the error itself is reporting as the issue):
The unwanted scheduling in order to save unticking the option:
Trying to enable the option while setting a later date and time (+ 3 days and 2 hours) to simply test what the error is reporting as the issue:
The resulting error:
Desktop (please complete the following information):
OS (ver): Windows 10 Pro (10.0.19042 Build 19042) & iOS (14.1)
Browser (ver): Brave (1.28.106) & Safari
Additional context
I feel like something in the latest patch has broken some exception ruling where if a child session is being set to start after an already scheduled parent, to then ignore any date or time pre-filled into the fields. Even clearing these fields (so they're blank when clicking "Schedule" to save the parent option) results in the same error.
Describe the bug Setting a child session to start after a parent session has ended (via the session schedule options) results in an error but the option still seems to apply (waiting to test if the session will actually start after the parent session though). Also unable to disable option anymore via "Remove schedule", instead having to click "Schedule" to save the option being unticked, which then schedules the session for the default date and time already entered, resulting in a further step to then remove that unwanted scheduling.
These issues only started occurring after patch v2.1.3 was applied, previous to that no error occurred and the option could be disabled via "Remove schedule".
To Reproduce Error
Cancelling
Expected behavior Enable child sessions to start when parent sessions have finished irrespective of date and time prefilled into schedule session popup and disable when needed.
Screenshots
Error after configuring a session to start after parent session (happens irrespective of prefilled date and time or setting a different future date and time to try and avoid the error due to what the error itself is reporting as the issue):![image](https://user-images.githubusercontent.com/87270602/130555189-cfcee6f2-0992-40c6-b20f-7f073b45da00.png)
The unwanted scheduling in order to save unticking the option:![image](https://user-images.githubusercontent.com/87270602/130555384-89b46e66-90f5-4df8-aee7-a41e36dbd7ea.png)
Trying to enable the option while setting a later date and time (+ 3 days and 2 hours) to simply test what the error is reporting as the issue:![image](https://user-images.githubusercontent.com/87270602/130555901-94e6f095-c4c1-4976-8c69-04e0a05d3f91.png)
The resulting error:![image](https://user-images.githubusercontent.com/87270602/130556116-43491792-b4f8-4faa-a517-49cc61ccff7c.png)
Desktop (please complete the following information):
Additional context I feel like something in the latest patch has broken some exception ruling where if a child session is being set to start after an already scheduled parent, to then ignore any date or time pre-filled into the fields. Even clearing these fields (so they're blank when clicking "Schedule" to save the parent option) results in the same error.