-
Suggestion
-
Resolution: Fixed
An administrator can select a dependency blocking strategy for a build plan, (on the Dependencies tab when editing a build), even if the build plan has no parent build.
This is redundant and potentially misleading. The UI should either prevent a blocking strategy from being selected unless a parent build is selected or have some sort of validation on the 'Save' button to prevent this from happening.
Since parent builds might be generated after the dependency blocking strategy is selected, (now that we have all that Maven generation etc), this can't be prevented from happening, but I'll add a note about it to the description section.