Skip to content
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

activity bump text is hard-coded at 1 hour #12130

Closed
stirby opened this issue Feb 13, 2024 · 0 comments · Fixed by #12170
Closed

activity bump text is hard-coded at 1 hour #12130

stirby opened this issue Feb 13, 2024 · 0 comments · Fixed by #12170
Assignees
Labels
bug Used to filter all bug issues s3 Bugs that confuse, annoy, or are purely cosmetic site Area: frontend dashboard

Comments

@stirby
Copy link
Collaborator

stirby commented Feb 13, 2024

The text in Workspace settings -> Schedule -> Autostop displays that the workspace will be automatically bumped by 1 hour when activity is detected.

This is now configurable, and should reflect the ActivityBump setting like the template settings schedule page does.

Screenshot 2024-02-13 at 4 14 16 PM

From workspace settings:
Screenshot 2024-02-13 at 4 17 45 PM

Location:

Set how many hours should elapse after the workspace started
before the workspace automatically shuts down. This will be
extended by 1 hour after last activity in the workspace was
detected.

@stirby stirby added site Area: frontend dashboard chore Non-customer facing refactors, cleanup, or technical debt. s3 Bugs that confuse, annoy, or are purely cosmetic bug Used to filter all bug issues labels Feb 13, 2024
@BrunoQuaresma BrunoQuaresma self-assigned this Feb 14, 2024
@BrunoQuaresma BrunoQuaresma removed the chore Non-customer facing refactors, cleanup, or technical debt. label Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to filter all bug issues s3 Bugs that confuse, annoy, or are purely cosmetic site Area: frontend dashboard
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants