Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • whats-open whats-open
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SRCT
  • whats-openwhats-open
  • Issues
  • #70

Closed
Open
Created Oct 28, 2017 by Andrew J Hrdy@ahrdyMaintainer

Schedule valid_start valid_end should be YYYY-MM-DDThh:mm:ssTZD

A schedule's valid_start and valid_end should be YYYY-MM-DDThh:mm:ssTZD instead of YYYY-MM-DD. In some scenarios, the current design can cause errors.

Example: A special schedule for Southside has Southside closing one day at 11pm instead of 2am the next day. But the valid_start and valid_end are only on the first day. If a user is viewing an application between 12am and 2am on the second day, then it would show that Southside is open because the main_schedule is used.

Edited Oct 30, 2017 by Andrew J Hrdy
Assignee
Assign to
Time tracking