Include room reservations/changes #66
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Chronos#66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In order to make it possible that teachers can reserve special rooms (e. g. computer room(s) or exam room).
There should be two options to do this:
LessonSubstitution)Event)I think we should add additional models for room reservations with foreign keys to
LessonSubstitutionfor lesson-based room changes andEventfor out-of-class reservations.Lesson-based room changes should be done directly from the timetable, maybe we can create a lesson page with options for this lesson. For reservations I would prefer a special form.
However reservations can only be done if the wanted room is free to the corresponding lesson(s) – but I think that goes without saying.
To make reserved rooms available in UNTIS directly we maybe can include an export to UNTIS which sets this directly in the database (big attention needed on securing data). If we do this, we will to have counter the issue when the corresponding item in UNTIS is changed – how to include this in Chronos? Deleting the reservation?
Advances #44
removed milestone
This issue became more urgent for the Katharineum and has to be done as soon as possible. Maybe we can add a milestone, @nik?
We can plan this for the next milestone after 2.0a2. We should not bloat 2.0a2 further, as it was defined as the set of features that choolApps had and we cannot implement arbitrarily many new features en passant.
Sounds like a good idea.
removed milestone
marked this issue as related to #119
mentioned in issue #119
marked this issue as related to #120