Allow A Project To Specify Default Iterations Sorting Order
Proposal
Desired change: Allow a project to have a default iteration to use in the context of creating a new issue. If you are using iterations at the project level, the default iteration on the issue creation is created via some complex rules. Per @leocuriel the rules are:
The default sprint cadence in GitLab is not ordered by last created or alphanumeric ordering. It is ordered by the Duration field, with the shortest cadence appearing first.
If all sprints are of the same duration and start and end on the same day, the default sprint cadence in GitLab will be selected based on the following rules:
The sprint that is closest to the current date.
If there are multiple sprints that are equally close to the current date, the sprint with the earliest start date will be selected.
For example, if the current date is 2023-08-15, and there are two sprints that are both 1 week long, the sprint that starts on 2023-08-15 will be the default sprint cadence.
With this behavior, if I have N teams, each with their own sprint cadence but with the same schedule (all teams start and end on the same day), contributing to the same repo this ruleset results in a seemingly arbitrary selection of default sprint cadence. Engineers who aren't paying attention will create tickets that end up in the wrong sprint cadence, which in turn impacts the iteration burn down and burn up charts as adding and removing tickets impacts the committed work line. Having the ability to configure the issue creation flow to either default to a specific iteration or default to no iteration would enable us to avoid the issue of issues going into the wrong iteration.