Guidelines for Effective Error Handling
A major usability testing finding was that error messages are lacking in Horizon. They are either too vague or don’t exist. We can improve this by proposing fixes to current error messaging and provide guidelines for error messaging in new features.
Related development blueprint in Horizon here: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Liz Blanchard
- Priority:
- High
- Drafter:
- Jacki Bauer
- Direction:
- Approved
- Assignee:
- Liz Blanchard
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Pieter
Related branches
Related bugs
Sprints
Whiteboard
According to Bruce Tognazzini’s Heuristics, a good error message should:
1. Explain what’s wrong
2. Tell the user specifically what to do about it
3. Leave open the possibility the message is improperly being generated by a deeper system malfunction
[5-28-2014 lblanchard] A first cut at an evaluation and a set of UI guidelines around Error Messaging can be reviewed on the wiki here:
https:/
Work Items
Work items:
Define proposal for error message guidelines from a UX perspective: DONE
Present proposal at OpenStack Summit ATL: DONE
Update guidelines based on feedback: INPROGRESS
Influence development blueprint with documented guidelines: TODO
