-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Epic: Admin dashboard enhancements to avoid SQL queries for support #7597
Comments
👋 @jldec I really like how you have this epic broken down, and the tasks in the epic link to issues. 👍 It would be helpful if users could force stop a workspace themselves, perhaps after a certain amount of time has passed (an hour?) since it started stopping. I say this because, right now, when a workspace is stuck in stopping, the user is dependent on an admin (Team Workspace usually), and this requires us to update the database manually (which doesn't scale well). WDYT? This would get the user access to their workspace sooner, reduce messages in Front, and cut down on manual tasks within Gitpod itself. |
@jldec Once you're back: can you look into splitting this up in follow ups? 🙏 |
Closing this because the Epic process requires epics to end.
|
Thanks for following up, @jldec! How is #8532 related to the epic btw, is it a typo? |
Yeah, that was a typo - thanks for noticing @laushinka |
Summary
The goal of this epic is to enable the use of the admin dashboard, to resolve support scenarios which currently require SQL queries for inspection or direct SQL manipulation of data.
Context
Features such as teams, or projects and prebuilds cannot currently be inspected via the admin dashboard. This makes it difficult to support users in their use of these features.
Issues with infrastructure scheduling may result in database inconsistencies which can currently only be resolved through direct SQL manipulation of the affected records. One examples of this is #7255.
Description
general
workspaces
user accounts
projects
teams
nice to have (not in scope for this epic)
Value
Visibility into Gitpod feature usage is important for customers and operators to understand how users are getting value from the platform.
The text was updated successfully, but these errors were encountered: