Iteration Naming

Problem

Some customers want to retain the ability to define a custom name for automated iterations. We also need to clean up the presentation of the programmatically generating iteration names we display in list views and dropdowns.

See example from a customer:

This is a question/SL2 for the team behind the new Iteration Cadence feature ( &5077).

My team currently has Iteration Cadences enabled for our Group (9942181), and we have two cadences setup at the moment, a two-week cadence and a four-week cadence:

We have been able to setup automatic iteration linking for our ongoing issues using a triage bot and quick actions. This requires us to programmatically know the name of our iterations. We have noticed that iterations in our 2022 cadence have been automatically named 'Iteration 1', 'Iteration 2', etc...

However we do not see a name given to the current iteration in the Monthly cadence:

I think this may be a bug - how does iteration name (not iteration cadence name) get set?

Proposal

• All iterations can have a custom name defined.
• Names in closed iterations can also be updated at any point in time.
• If a custom name is defined, used that to display the iteration information in the issue sidebar, board list, iteration cadence iteration list, filter bars, etc.
• Update the display of the generated iteration name to be consistent in the issue sidebar, board list, iteration cadence iteration list, filter bars, etc.
• The current proposal for the generated name is - {{Cadence Name}} {{sequence #}}

Acceptance

• Authorized user can add a custom name to an iteration
• Updating the name works equally for open and closed iterations.
• If the custom name is present, use that instead of a programmatically generated name
• The updated generated name is consistently used everywhere iterations are referenced.

Availability and Testing

Manual job package-and-qa will need to be run in the MR(s) that introduces the change.

Ensure test coverage in unit/integration tests.