Be more clear why saving fails when it fails #225
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
servala/servala-portal#225
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
When saving fails, the form just tells the user "We could not save your changes.".
The error message should tell the user why daving fails.
Steps to Reproduce
Be more clear when saving fails why it failsto Be more clear why saving fails when it failsAt this point, users see error messages with details for at least some conditions, including a call to action to contact support. In most cases, the error message should also be placed at the form field in question. Is there any other particular case that needs handling?
Not that I'm aware off. What I've seen is that sometimes the error message is displayed twice:
"We could not save your changes" is displayed when something is wrong with the form, right? And the error is displayed inline? If this is true, and I think so, then we're good as it is. But we might want to rephrase this a bit: "Please review and correct the errors highlighted in the form below."
I think the confusion comes from the "expert form", because if there was an error in one of the tabs, it wasn't directly clear what's wrong.