Release Cascade default

[Gary Voss]

Is there a way to change the release cascade option default to No?

[Sagi Gabay]

Hi Patrick.

What do you mean by "Release Cascade"?  Do you mean the checkbox option named: "Copy current and future Releases and Iterations from parent project" that you have when creating a new project?     If that's what you mean then the default for this checkbox is 'Yes'.

Will appreciate your clarification.

Thanks,
Sagi

[Heather Kanser]

Hello Patrick,

I am agreeing with Sagi.  There is no way to change the default value for this toggle.  Please feel free to add a request for that functionality using the Feedback button.   Most customers always want to cascade the Iterations and Agile Releases.  Can you provide more information on why you wouldn't want the cascade the timeboxes to the child teams?

Cheers,
Heather

[Christopher Pola]

Hello @Sagi Gabay, I think @Gary Voss means the Cascade toggle when creating a new Iteration or Release Timebox.

+1 to what @Heather Kanser mentioned. Most customers adopt the principle of Cadence and Synchronization for these planning timeboxes. These timeboxes are designed to help planning at scale, planning increments vs. a physical deployment or 'release' or version of software.​ You can use them for either purpose but we might have different strategy or approach if your Timeboxes are intended for a 'deployment'. That is just a guess about what you might be trying to achieve or doing @Gary Voss.​​​​

Principles of Cadence & Synchronization: https://www.scaledagileframework.com/apply-cadence-synchronize-with-cross-domain-planning/

[Gary Voss]

Yes, @Christopher Pola, that's is exactly what I was referencing.   We use the release option for physical deployment of software and the cascade option is not helpful for the child project areas (which creates a lot of unneeded releases at child projects when people forget to uncheck).  I'll read the link you posted to better understand Cadence and Sync.   Thanks for the quick response.​