Skip to content
GitLab
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 35
    • Issues 35
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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
  • AlekSIS®AlekSIS®
  • Official
  • AlekSIS-App-Chronos
  • Issues
  • #161
Closed
Open
Issue created Jan 06, 2022 by Dominik George@nik🍻Owner

Manage basic data in frontend

In order to move towards creating timetables (#35), we should start by allowing managing of the basic data behind timetables in the UI. These are:

  • Validity ranges
  • time periods (existing MR !196 (closed) might be helpful, or not)
  • subjects
  • rooms
  • Holidays

This issue is strictly limited to managing these data, as everything else needs more coplex UI to get relations right.

I am not yet sure whether we should turn this into one page for all basic data (maybe using tabs), or several pages (opinions please, @ZugBahnHof @yuha @hansegucker)

Assignee
Assign to
Time tracking