Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • engine engine
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • AURAAURA
  • engineengine
  • Issues
  • #52
Closed
Open
Issue created Nov 10, 2020 by David Trattnig@davidOwner3 of 3 checklist items completed3/3 checklist items

Show and Schedule Fallbacks should behave like "default playlists"

  • Add "show_default" and "schedule_default" playlist relations to timeslot
  • They should behave similar to the station fallback, but no email to coordinator is sent instead and there's no "jumping" between sources
  • Check if it's required to adapt the playlog/clock. Default playlists are not handled like "real" fallbacks for RTR reporting
Edited Dec 16, 2020 by David Trattnig
Assignee
Assign to
Time tracking