Skip to content

Remove feature flag check from iteration cadences resolver

Mario Celi requested to merge 300897-create-issue-with-iteration-no-cadence-specified into master

What does this MR do and why?

Follow up on !71689 (merged)

iterationCadenceId is mandatory when iterationWIldcardId is specified. So, we needed to make the cadence resolver available even if the feature flag is disabled.

Even if the feature is not generally available right now, this seems like the best way to go in order to make the API consistent (you always need to provide a cadence ID when using the wildcard ID). The down side of making cadence ID mandatory only when the feature flag is enabled is that it would be a silent breaking change once the FF is enabled.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

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 #300897 (closed)

Edited by Mario Celi

Merge request reports