Add permissions (via rules) #93
No reviewers
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
mysql
part
non-technical
part
packaging
part
xml
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-Untis!93
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rules-and-permissions"
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?
changed milestone to %"2.0a2"
Do we need these? Isn't more or less a question of permissions on Chronos? If someone has all permissions to do the stuff in CHronos, they probably are also ok to do it through an import.
Any argumentation in favour of having separate permissions for the importers?
OK, yes, maybe we want this as a way to express that a user can upload XML, but not do manual amendments.
resolved all threads
merged
mentioned in commit
15b7f12db8