[BUG] Newly created sprint is created in the "closed" state, making it unusable in the backlog view

[gantaa]

Describe the bug
I believe the bug only occurs when being late to create a sprint that is CURRENTLY underway. For example: when the last created sprint has ended in the past few days, and I am a little late to creating the current sprint.

On the form where the new (current) sprint is created, the default selected dates are Sunday -> Sunday. If those values are used, the sprint is created as expected. However, if I manually change the start date of the sprint to Monday -> Sunday the sprint gets created but appears at the top of the "Show closed sprints" section, and is unusable because stories in the backlog cannot be dragged to it.

How can we reproduce the behavior

1. If necessary, configure your sprint cadence in the project to be 2 week Sunday -> Sunday sprints.
2. Make sure you're creating a sprint where todays date is within your sprint timeframe, and the last created sprint has already ended in the past.
3. Navigate to the backlog view and click + Add for a new sprint.
4. The form will give you default dates (and hint for sprint naming) based upon the last created sprint.
5. Change the sprint start to the Monday following the currently selected Sunday (The next day)
6. Save the sprint and observe that it appears in with all the other "closed sprints", and not at the top of the backlog sprints

Workarounds
I use the Sunday -> Sunday schedule and let go of my OCD of wanting the sprint to start on Monday. And the sprints get created fine if i don't touch the default dates in the form.

Screenshots
Sorry. forgot to grab one

Taiga environment
Taiga.io

Desktop (please complete the following information):
OSX12.4
Chrome
Version 102.0.5005.61 (Official Build) (arm64)

Additional context
i had to click "show closed sprints" to see my newly created sprint, even though "right now" was within the sprint's timeframe