You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of scrumlr, I want to know what is the problem if the service is not available (i.e., prod is down). Instead of looking at a blank screen or a browser-displayed error, I want to see a page telling me that the service is currently not available and that I should try again later.
For example, this is want OpenAI's page for this looks like:
This could be implemented using a service-worker: When a user opens scrumlr for the first time (while the service is available), this page is cached on the client. Then, when the client can't reach the backend in the future, the cached error page is displayed.
We don't need a new design for this, we can just use the existing error page, change the text and omit the error code.
The text was updated successfully, but these errors were encountered:
As a user of scrumlr, I want to know what is the problem if the service is not available (i.e., prod is down). Instead of looking at a blank screen or a browser-displayed error, I want to see a page telling me that the service is currently not available and that I should try again later.
For example, this is want OpenAI's page for this looks like:
This could be implemented using a service-worker: When a user opens scrumlr for the first time (while the service is available), this page is cached on the client. Then, when the client can't reach the backend in the future, the cached error page is displayed.
We don't need a new design for this, we can just use the existing error page, change the text and omit the error code.
The text was updated successfully, but these errors were encountered: