When migrating from a manual to automated cadence, iteration dates are incorrect
Problem
Just recently gitlab enforced that we setup an automatic iteration cadence for our sprints. Fine. I went through the process and had it setup 4 iterations in advance. Then I noticed it SKIPPED a week and I cannot add that additional week in. Seeing that, I went ahead and created a new cadence that starts today 5/18 and used that. Now, however, I can't discontinue the OLD cadence -- it will keep going forever. I can't delete the old cadence because it will delete the old iterations (this was verified through gitlab issue history) and dissociate the issues from the deleted iterations. (We use the iterations for custom developer analytics.) internal support ticket
After converting an iteration to an automatic cadence, due to the way in which GitLab handles iterations, there is now a 7 day gap between the end of the current iteration and the start of the next. There is no way of changing the start date, or moving any of the automatically created iterations to match up with the teams current cycle. The only solution seems to be to create a new iteration cadence, and then delete the old one. This results in deletion of historic sprint data as well....the date ranges vary per team. In this particular case, the first sprint we set up when moving to GitLab was set to start on a Thursday but after learning more about how iterations work, we changed this in the following sprints to start on a Friday. With the new cadences however it is using the first date of the sprints that was setup and there seems to be no way to alter this. This could be a very big issue for any of our teams going forward if they need to change their sprint cadences. We can’t have past iterations deleted every time.”
How can I stop the cadence without deleting it, because I don’t want to delete previous iterations?
Potential root causes
- The start date of the first iteration is set automatically but the manually scheduled date ranges did not follow a predictable cadence. (ex: switching the day of the week to start iterations at some point, not including weekends when manually scheduling iterations so the end date of the most recent manual iteration was a Friday but the next iteration shouldn't have started until Monday)