Under: ☂️ #12332

A list of e2e flows for scheduling and some related issues.

Issues related to scheduling instability

• Workspace Activity
  • bug: opening workspace details in UI can cause activity bump #12304
  • Autostop keeps refreshing even though workspace is not used #12012 (2.7.2)
  • bug: last_used_at not updated when "activity" is sent via API /report-stats #11986
  • Coder "app" connections are not recorded as workspace usage for the purposes of detecting idle state #11812
• Autostop configuration
  • autostop ignores template level config if turned off at workspace level #12124
  • Autostop maximum appears busted/blocked. #11990
  • Time until autostart not indicated on dashboard #11781
  • Workspace Autostop settings displaying incorrect value when template is updated #11471 (needs reproduction)
  • bug: existing workspace shows old Autostop value after template's Default autostop changed #10636

E2E Flows

May need additions.

Admin flows

• Autostop
  • Admin applies autostop change to template via UI/CLI
    • Does this change propagate to all workspaces upon update
  • Admin enables customization of autostop for workspaces under template
    • Does the autostop default propagate to workspaces
    • After updating, is autostop mutable
  • Admin disables autostop
    • Workspace autostop configuration is overridden
  • Admin sends bump to workspace via CLI
    • Is this overridden by autostop requirement
    • Does the workspace allow indefinite activity bump without MAX_TTL, autostop requirement
    • Related: Autostop maximum appears busted/blocked. #11990
  • Is workspace considered active when…
    • coder_apps are in use
    • user is connected via ssh
    • Ports are forwarded from the workspace
    • Related: bug: opening workspace details in UI can cause activity bump #12304
• Autostart
  • Admin applies autostart change to template via UI/CLI
    • Does this change propagate to all workspaces upon update
  • Admin enables customization of autostop for workspaces under template
    • Does the autostop default propagate to workspaces
    • After updating, is autostop mutable
  • Admin disables autostop
    • Workspace autostop configuration is overridden
• Dormancy
  • Workspaces are cleaned up by admin-enabled workspace dormancy
• Autostop Requirement
  • Does the requirement only kick in at the start of quiet hours
  • Does the requirement shutdown without quiet hours configured

User flows

• Autostop
  • User can override default autostop when permitted
  • Users can manually bump autostop
    • via GUI
    • via CLI
• Autostart
  • Users can configure autostart days when permitted by template admin
• Quiet hours
  • User configured quiet hours override admin defaults