Notification for changes in the substitution plan #50
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#50
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?
AlekSIS core has an advanced notification framework now. Changes in the substitution plan should trigger notifications to the relevant persons by adding a Notification object. It is up to the core to decide which channels to use for the notification.
This should best be done in the
clean()orsave()methods of the related models or using signals (while some people consider signals an anti-pattern).https://nextcloud-talk.readthedocs.io/en/latest/
We should discuss this issue in regard of a globally usable notification app.
changed title from {-Benachrichtigungen für Stundenplanänderunge-}n to {+Notification for changes in the substitution pla+}n
changed the description
changed the description
changed milestone to %"2.0a2"
unassigned @hansegucker
removed milestone
assigned to @hansegucker
created merge request !546 to address this issue
mentioned in merge request !546
mentioned in commit
6f667b881b