Automate an Iteration Cadence
Problem to solve
This is part of a workstream to automate iteration cadences and support more flexibility for teams that share projects. The full problem statement can be found here -- &5077
Proposal
- BE
- handle automatic creation of iterations within a cadences
- have a background job that generates future iterations based on future iterations setting
- when the option to automatically roll open issues from a closed iteration to the next iteration is enabled, automatically move open issues to the next iteration and ensure the
relative_position
of all issues rolling over is higher than the other issues that are also in the next iteration. - background job tied to iteration close event to move issues to next iteration
- handle automatic creation of iterations within a cadences
- FE
- handle iteration source change
- dropdown to pick new iterations source
- UI/UX to handle the change of the source, maybe some wizard to map iterations from one source to another to allow for issues migration ?
- handle iteration source change
This is the third step towards &5077 (comment 467401527)
Further details
Allows historical data to be migrated into the project from external services.
UX & Vertical Feature Slices
-
I can disable Automated Scheduling
(default to enabled) -
If Automated Scheduled
is disabled, I cannot change or interact with any other fields exceptDescription
,Name
, andRoll Over Issues
. -
I can enter the start date for the first Iteration. -
I can select the duration (in weeks) for each Iteration within my cadence from a drop down list with values of 1
,2
,3
,4
,5
, or6
-
I can select the number of future iterations i want to always have automatically scheduled from a list with the following values -- 2
,4
,6
,8
, or10
-
All fields are required except Description
andRoll Over Issues
, whenAutomated Scheduling
is enabled. When it is disabled, onlyName
is required.Roll Over Issues
andAutomated Scheduling
is enabled by default for new cadences. For existing cadences,Roll Over Issues
is enabled by default. -
When Automated Scheduling
is enabled and the required fields are defined, I can either click a button to create the cadence or to cancel the creation process.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.