Check permission rules if they handle lessons with substitutions correctly #147
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-Alsijil#147
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?
Currently, original teachers don't get access to their lessons if there are substitutions assigned to this lesson. This has to be fixed and we should check if there any similar issues.
created merge request !548 to address this issue
mentioned in merge request !548
When drafting the access model in Alsijil, compeltely transferring the complete teacher role to a substitution teacher was intentional because only one teacher should be able to author notes for a lesson at any given time.
If this is to be changed, it needs to be discussed.
Yes, you're right. But the original teacher should be able to view the notes for the lesson at least. I will check that again.
Then again, we already depart from that, because nowadays lessons can have more than one teacher. Thus, we should probably treat substitutions the same as co-teaching…
Then I can remove the last commit?
First, you should provide argumentation. If you support my first position, or maybe the option to make the lesson read-only for the regular teacher, please document why. (Same for all other options; we should not make changes because someone says it might be a good idea without reasoning).
I think we should make the lesson writable for the original and the substitution teacher because of the following points:
Do we have a mechanism to notify the original author of a lesson documentation if it is changed by someone else afterwards?
In addition to the change history, nothing.
Please open an issue to implement that, then, and link it as follow-up issue in your MR.
marked this issue as related to #148
Now tracked in #148
mentioned in commit
e94a0e7a15