Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat: ui: show next scheduled autostart/autostop time #1059

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

Closed
Tracked by #850
johnstcn opened this issue Apr 18, 2022 · 7 comments
Closed
Tracked by #850

feat: ui: show next scheduled autostart/autostop time #1059

johnstcn opened this issue Apr 18, 2022 · 7 comments
Assignees
Labels
site Area: frontend dashboard
Milestone

Comments

@johnstcn
Copy link
Member

johnstcn commented Apr 18, 2022

What

Show the next scheduled workspace autostart/autostop time in the UI on the workspace detail page, in the WorkspaceSchedule component.

This can be consumed from the API endpoint GET /workspace/:id/auto(start|stop)

Why

As a user, I want to see when my workspace will start.
For example, given:

  • It is currently 09:01
  • My workspace is scheduled to start every day at 09:30
  • My workspace is currently off

When I look at the workspace detail page for my workspace,

Then I should see, under Workspace Start ($TIMEZONE): 09:30 (in 29 minutes)

Similarly, I should also see the next scheduled autostop time if it is enabled for my workspace and my workspace is currently running.
If autostart or autostop is not enabled, for my workspace, I should just see the text "Manual".

(This is intended to be worked on as part of the TDD work session at the engineering off-site.)

@johnstcn johnstcn added the site Area: frontend dashboard label Apr 18, 2022
@johnstcn johnstcn added this to the V2 Beta milestone Apr 18, 2022
@BrunoQuaresma
Copy link
Collaborator

The FE right now shows enough information for the user and it is already tested.

@misskniss
Copy link

This was closed because it was no longer needed.

@ammario
Copy link
Member

ammario commented May 12, 2022

@misskniss why is this considered no longer needed?

@tjcran
Copy link

tjcran commented May 12, 2022

@misskniss why is this considered no longer needed?

@ammario I think the comment was unclear. The issue was no longer needed because the work was already done. A screenshot or visual helps in cases like this. I just created this workspace. I didn't specify a start/stop time, but this is the workspace detail page where it is present. I'll get an example image where start/stop are specified as well, because that will also be showing.

image

@ammario
Copy link
Member

ammario commented May 12, 2022

Understood, thank you.

@greyscaled
Copy link
Contributor

I did this work in #991

I'll just re-allocate the ticket to me

@greyscaled
Copy link
Contributor

greyscaled commented May 14, 2022

OK, so Zenhub (not going to lie, I'm not a fan) has this listed as an epic. That's because I accidentally converted this to an epic, and I can't seem to undo that operation.

This ticket was done a while ago, but then retroactively added to #850 for posterity.

I apologize for the noise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
site Area: frontend dashboard
Projects
None yet
Development

No branches or pull requests

6 participants