Custom Iteration Cadence Start/End Date
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
A customer is requesting to be able to set the start/end date of an iteration cadence, then progress to the next iteration cadence.
Relevant customer info:
- US Federal ticket (Internal access to verified US Citizens only)
- SFDC (internal)
At present, their organizational sprints are set to start on the 1st of each month, then end on the 15th. The next sprint would start on the 16th of each month, until the end of the month (~2 week sprints). With the current iteration cadence design, a duration of every 2 weeks wouldn't suffice as the end date may not align with their sprint end date.
Edited by 🤖 GitLab Bot 🤖