Skip to content

Improve paused prebuilds alert #14294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gtsiolis opened this issue Oct 31, 2022 · 1 comment
Open

Improve paused prebuilds alert #14294

gtsiolis opened this issue Oct 31, 2022 · 1 comment
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

Comments

@gtsiolis
Copy link
Contributor

gtsiolis commented Oct 31, 2022

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:

  1. The paused prebuilds alert is not visible in the prebuilds page, which is the most relevant page for this message.
  2. The latest prebuild information on the project card is accurate, but possibly irrelevant and not useful.
  3. Clicking the action (link button) to resume prebuilds, breaks the layout of the alert message, keeps the alert on visible, is updating the link color to be the same as the rest of the alert message, etc.

See also relevant discussion (internal). Cc @AlexTugarev @jldec

Branches (project default page) Prebuilds Project Resuming Prebuilds
paused-1 paused-2 Screenshot 2022-10-31 at 5 22 41 PM Screenshot 2022-10-31 at 5 33 29 PM copy

Proposal

TBD (To be discussed)

In the meantime, here are two approaches to consider doing as minimal viable changes (MVCs):

🅰️ Move the alert to the top of the prebuilds list as an in-page alert.
- 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)

🅱️ Move the alert to the top of the branches and prebuilds page.
- 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. ➰

@gtsiolis gtsiolis added component: dashboard feature: prebuilds type: improvement Improves an existing feature or existing code team: webapp Issue belongs to the WebApp team labels Oct 31, 2022
@stale
Copy link

stale bot commented Feb 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Feb 5, 2023
@gtsiolis gtsiolis added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant