Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A AlekSIS-App-Chronos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • 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
  • AlekSIS
  • Official
  • AlekSIS-App-Chronos
  • Issues
  • #122

Closed
Open
Created Mar 25, 2021 by Jonathan Weth@hansegucker⌨Owner

next_lesson doesn't correctly work with changing validity ranges and probably also year changes

Currently, there are multiple issues:

  • next_lesson is used on a queryset with lesson periods from multiple validity ranges.
  • Selecting the next item just by index (or, if there is no next item, selecting the first item and switching the week) doesn't work if there are lesson periods from multiple validity ranges.
  • Also, year changes doesn't work correctly if there are multiple validity ranges.
Assignee
Assign to
Time tracking