Skip to content

Name automated iterations based on cadence title

What does this MR do and why?

Currently iterations created by a cadence are all named Iteration X, this is troublesome because if you have more than 1 cadence (we have 6 at the moment), it isn't possible to know which iteration belongs to which team.

This MR updates the automated cadences to be named based on the cadence title.

Screenshots or screen recordings

I'm unable to get cadences working locally at the moment. The screenshots would just show iterations with different names though. I think the tests show it better.

How to set up and validate locally

Create a new iteration cadence and the iterations created should be names #{cadence.title} X instead of Iteration X.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #349518

Merge request reports

Loading