-
Epic
-
Resolution: Done
-
Major
-
None
-
Blueprint names are prepopulated
-
8
-
False
Goal:
- A user creating a blueprint should never be presented with a disabled "Next" button.
- Blueprints require a name. The name field should be prepopulated so users are not blocked by this step.
Acceptance Criteria:
- On the "Details" step upon creating a new blueprint, the field for the blueprint name will be prepopulated like so: "$OS $ARCH $TARGETS $DATE". For instance, "RHEL9 X86_64 AWS Azure 30 July 2024".