Hi Ignacio
This can be achieved by creating a new release indicator and maintaining changeability value according to your requirement. For example, in your case, you have two requirements.
For all release strategies where you want the system to not relaunch again, create a release indicator with changeability value 1 (Cannot be changed) and maintain that release indicator in the release strategy at release statuses step and vice versa.
| User | Count |
|---|---|
| 91 | |
| 8 | |
| 6 | |
| 6 | |
| 5 | |
| 5 | |
| 5 | |
| 5 | |
| 5 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.