Cannot start new Sprint

[Rolf Englputzeder - SAVVY_ Telematic Systems AG]

We keep getting issues when starting a new Sprint. This time this:

Problem: Attempting to start a new Sprint

Description:

• The Sprint is marked as completed, and tickets have been moved to "SSES Sprint 226".
• The Sprint "Wartesaal (Waiting Room)" appears at the top of the list unexpectedly.
• However, this Sprint is part of the Backlog and should be moved to the end of the queue.
• All attempts to adjust this sorting fail.
• Consequently, starting a new Sprint is not possible.
• The Sprint "Wartesaal" is now always displayed at the top of the Backlog view, making it the only Sprint that can be initiated.
• Attempts to shift this or any other Sprint result in failure.

General question: Starting a new Sprint is always a headache, because Jira keeps changing their system (we had often the issue that Ticket does not move from current Sprint to the next Sprint automatically). Any outlook when Jira is stable again? Are the big refactorings / vibe codings etc. on-going? Becaues all of those features worked very well before...

[Marc -Devoteam-]

Hi @Rolf Englputzeder - SAVVY_ Telematic Systems AG 

On the backlog, sprint on top is based on start date of the sprint set or empty.

Issues, by default don't move to the next sprint, this is asked when closing the Sprint, what to do with the open issues in the sprint.

If you scroll past sprint "Wartesaal", do you see other sprints, before the "backlog" section.

Simple, check, collapse sprint "Wartesaal"

Are 3rd party apps used in the instance, they can cause behaviour issues, are you using the latest version update of your used browser?

[Thomas Zürz]

Hi Marc thank you for your fast reply.
> On the backlog, sprint on top is based on start date of the sprint set or empty.

This is not true, the Sprint we talk about had no date at all. We added an date that points in the future, for testing purpose, but the sprint stay on top, Then we moved the date in to the passt. But also this was not working at all. The sprint "Wartesaal" stay on top. We also asked Rovo and it acknowlaged that "Wartesaal" needs to started next. To continue our work and get not always interupted with our work by Jira we tagged the tickets with "Wartesaal" and moved them into the backlog. 

> Issues, by default don't move to the next sprint, this is asked when closing the Sprint, what to do with the open issues in the sprint.

That is correct and we moved tickets to the next Sprint.

> If you scroll past sprint "Wartesaal", do you see other sprints, before the "backlog" section.

For testing purpose we also try to move other sprints up or down... with the same unexpected result. Nothing could moved. Start sprint "Wartesaal".

With an empty "Wartesaal" we was able to start the sprint. But as like in the past we faced issues with the Ticket assignment. And the move to new sprint option did not work like it should and we lost again tickets from the next sprint that was in the status progress or test.

[Marc -Devoteam-]

Hi @Thomas Zürz 

Can you provide screenshots.

And as you are referring to Watesaal in German, this translates to Backlog in English.

This is not a Sprint, but this is the Backlog, all items not in a Sprint.

Are all items in the Sprint from a single project, or items from multiple projects?

Example from my end: