rk@tigase.net opened 2 weeks ago
-
Estimated Effort
Total estimate: 2.5 – 3.5 hours
Breakdown
- Analysis & classification of error types: 30–45 min
- UX decision & wiring (toaster vs persistent error): 45–60 min
- Frontend implementation (modal/banner component + wiring): 60–90 min
- Regression testing & polish: 30 min
This assumes:
- No backend contract changes
- Existing error messages are reused
- Frontend already has a modal or banner component that can be reused or lightly adapted
Work Log
Investigation
- Observed that fatal and blocking errors are displayed exclusively via transient toaster notifications
- Confirmed that toasters auto-dismiss, causing loss of critical error information
- Verified this behavior occurs during normal workflows and startup failures
- Issue was explicitly noticed during review and impacts usability and diagnosability
Root Cause
- All error paths currently funnel through a single toaster-based notification mechanism
- No distinction is made between informational messages and serious/fatal errors
Fix Strategy
- Introduce a severity distinction for frontend errors (e.g. INFO vs ERROR/FATAL)
- Route serious errors to a persistent UI element (modal or banner)
- Keep toaster notifications for non-critical messages only
- Ensure persistent errors remain visible until explicitly dismissed by the user
Validation
- Confirm serious errors remain visible until acknowledged
- Confirm minor messages still behave as transient toasters
- Verify no regression in existing success/info flows
Risk
Low. Changes are isolated to frontend error handling and do not affect backend logic or data.
-
-
Being fixed in an existing branch: feature/SZ-50-Issue-Management-UI
-
Previous Value Current Value Open
In Progress
-
Previous Value Current Value In Progress
Closed
| Type |
Bug
|
| Priority |
Blocker
|
| Assignee | |
| Version |
1.0
|
| Sprints |
n/a
|
| Customer |
n/a
|
Issue Votes (0)
Watchers (3)
Summary
Fatal and serious errors are currently displayed using transient toaster notifications that disappear automatically after a few seconds. This makes it difficult or impossible for users to read, understand, or act on critical error information.
Problem
Toaster notifications work well for:
However, they are not appropriate for:
When a serious error is shown in a toaster:
This issue was observed during normal usage and explicitly noted during review.
Expected Behavior
Suggested UX Direction (non-binding)
One of the following (or equivalent):
The key requirement is persistence, not a specific UI component.
Acceptance Criteria
Notes
This is a usability and reliability issue, not a backend or business-logic defect.