Improve paused prebuilds alert #14294
Labels
component: dashboard
feature: prebuilds
meta: never-stale
This issue can never become stale
team: webapp
Issue belongs to the WebApp team
type: improvement
Improves an existing feature or existing code
Problem to solve
Following up from #14081, the new paused prebuilds alert successfully informs users about this system change and provides an action to resolve the alert.
However, there are a couple of issues that come with the current approach:
See also relevant discussion (internal). Cc @AlexTugarev @jldec
Proposal
TBD (To be discussed)
In the meantime, here are two approaches to consider doing as minimal viable changes (MVCs):
- This way, we lower the risk of running into seeing multiple alerts racing for user's attention (see local preview alert[1], usage limit alert[2], etc)
- This is one of the most critical system status messages for a project in Gitpod, and moving this to the top of the page provides better visibility of system status.
In both cases🅰️ /🅱️ , there's no need to maintain the trigger state inside the alert when resuming prebuilds. Instead, we could a) redirect to project prebuilds and b) populate the prebuilds list with the newly triggered prebuild as user feedback.
Other things to consider for next iterations include updating the project card so that the prebuilds paused state is also visible from the team page where all projects are listed. ➰
The text was updated successfully, but these errors were encountered: