Auto calculated and manually set sprint dates broken

[Grigori Prokhorov]

Hi there,

I'm in the process of trying out a new organisational structure for our project.

For this I've set up a new Scrum based project and created:

• 2 dummy Epics
  • with 2 dummy issues, each
• 4 dummy Sprints
• 8 dummy Releases

Now, I've tried to set up the sprints in a "mixed" mode:

The first sprint starts whenever and then goes to the next week's wednesday.
All subsequent sprints should be 1 week long. The first "auto length" sprint should start on the wednesday the first sprint ends and then go till the next wednesday, and so on for all others.

Now, I had the following exemplary timeline in mind:

Sprint 1: 10/17/2022 - 10/26/2022 (10 days)
Sprint 2: 10/26/2022 - 11/02/2022 (7 days)
Sprint 3: 11/02/2022 - 11/09/2022 (7 days)
Sprint 4: 11/09/2022 - 11/16/2022 (7 days)

What I got instead is:

Sprint 1: 10/17/2022 - 10/26/2022 (10 days)
Sprint 2: 10/25/2022 - 11/01/2022 (7 days) but starts 1 day earlier than intended
Sprint 3: 11/01/2022 - 11/08/2022 (7 days) but starts 1 day earlier than intended
Sprint 4: 11/08/2022 - 11/15/2022 (7 days) but starts 1 day earlier than intended

Manually changing the sprint dates doesn't work. I can make the changes and they're shown in the "Backlog" view but they don't persist after a reload.
I've tried deleting the sprints and recreating them from scratch but some sprints were created with preset dates even though they should've been completely new records.
I've tried setting the sprint dates to "custom" and putting in the dates manually, I've tried setting them to "1 week" and re-selecting the start date.

Nothing works and new sprints seem to be automatically adjusted to start after the last "faulty" sprint. So when I added a Sprint 5 (11/16/2022 - 11/23/2022) the sprint got moved up 1 day to 11/15/2022 - 11/22/2022 without me even doing anything other than adding the sprint and reloading the page.

If I could just delete all sprints and recreate them properly, this would be manageable but even then - if this were to happen in an active project, this could necessitate a huge amount of re-work which is not optimal, to say the least.

Does anyone have any idea as to how to work around this?

Thanks
Grigori

[Sebastian Krzewiński]

Hi @Grigori Prokhorov 

Please ask atlassian support about that. I don't see any good explanation for that.

Regards,

Seba