-
Improvement
-
Resolution: Unresolved
-
Major
-
-
1.0-m10, 1.0-b05/b-06
Design Brief
Blue Ocean makes a lot of asynchronous rest calls and any of them could fail at any time.
There are two cases here I think we need to handle:
- When a whole page fails to render
- When one of the AJAX calls fails with 500/503/502 we should show the error screen
In Scope
- Design for both the cases above
- Decide what our error reporting should look like across the app.
Design
- Whole page fails to render
- Invision https://invis.io/648R3HVAV#/213891534_Error_-_500
- Zeplin https://zpl.io/Z1hPPwx
- AJAX Fail
- Invision https://invis.io/648R3HVAV#/213891533_Error_-_AJAX_Fail
- Zeplin https://zpl.io/21YQPC
- blocks
-
JENKINS-40032 Handle errors and 404s consistently
-
- Closed
-
-
JENKINS-38946 Failed API calls not handled very well
-
- Resolved
-
- is duplicated by
-
JENKINS-40032 Handle errors and 404s consistently
-
- Closed
-
-
JENKINS-35792 User needs to see better error pages
-
- Resolved
-
- relates to
-
JENKINS-42921 Error "toast" popup for unhandled errors on the client to do with fetching (500 error class) with opt out
-
- Closed
-
@brody Not very fond of the loading error, it's not very noticeable (from experience using the toasts during running, of course somewhat subjective - the normal spot for toasts is on the top) it doesn't look like an error, and the likelihood a reload would actually fix it is low, it's probably due to a data change on the back end.