How to set a Build as default?

While creating a new build, the Set Default drop-down with Yes/No options is available to mark the build as default.

Set Default - Yes : The build will be set as a default build on the execution screen for the selected Release Cycle combination.
- Testers do not need to remember and set the build manually every time. This also helps them to reduce build association errors.
- QA Manager can always set the current build as a Default Build to ensure the executions are always associated to the current build.
- Only one default build can be set for a given combination of a Release Cycle.
Set Default - No : Makes the Build as non-default. When some other build is set to default, this flag will be set to “No” for the previously default build.
Edit Build and Set it as Default
- On the Edit Build screen, users can edit existing build data and also add new release and cycle with default build value in edit build screen.
- While editing an existing build, the Set Default toggle option is available. Turn the toggle ‘On’ to mark the build as default for the Release and Cycle combination.
You can mark the build as default either while adding new Release(s) & Cycle(s) to the build. You can mark the build as default build for multiple combinations of Release(s) & Cycle(s) at a time.
You can mark the build as default after adding new Release & Cycle to the build.