-
Notifications
You must be signed in to change notification settings - Fork 334
Form validation #13937
Copy link
Copy link
Open
3 / 113 of 11 issues completedLabels
EpicQA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thisIssues that engineers have written automation around so QA doesn't have look at thisarea/form-validationheadlineHeadline item being tracked at top-levelHeadline item being tracked at top-levelpriority/0
Milestone
Metadata
Metadata
Assignees
Labels
EpicQA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thisIssues that engineers have written automation around so QA doesn't have look at thisarea/form-validationheadlineHeadline item being tracked at top-levelHeadline item being tracked at top-levelpriority/0
Type
Fields
Give feedbackNo fields configured for issues without a type.
Investigate and integrate the possibility of validating Rancher forms more effortlessly, replacing current logic.
Current plan:
Optionals:
@edenhernandez-suse for remaining inputs used in the form (e.g. radio group, array list)As this operation seems to require some redesign, it will be excluded from the epic anything about new designs