Resolve "Notification for changes in the substitution plan" #546
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
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!546
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "50-notification-for-changes-in-the-substitution-plan"
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?
Closes #50
assigned to @hansegucker
added 2 commits
Compare with previous version
changed the description
marked the checklist item Send notifications only when the object affects a specific time period in the future (next day, 24/48 hours, something like that) as completed
added 1 commit
Compare with previous version
marked the checklist item Site preference for globally activating/deactivating notifications as completed
marked the checklist item Person preference for activating/deactivating notifications as completed
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
marked the checklist item Preference for point of time when notifications for longer existing objects should be sent (see above) as completed
changed the description
marked this merge request as ready
assigned to @nik and unassigned @hansegucker
TODO:
marked this merge request as draft
Please move this below the imports
Don't use
Dict,List, andType.Don't type
kwargs.Much of this looks as though it should go into the template. But I might be mistaken.
Missing doc string (it is a private method, but yet...)
That doesn't calrify the need for the above private method. Please document why this feature needs to run code post-migration.
Missing doc string
Why does this need a getter method?
WHy don't we send notifications imemdiately when the change gets known?
Into which template?
The TeacherPropertiesMixin used in this model depends on a
get_teachersmethod. So, before the methods and properties provided through the mixin weren't usable.We do that for changes which affects the current/next day. But if there is a newly created substitution for in two weeks, we don't want to send a notification two weeks in advance.
Into the notification templa… oh, we don't have templates for notifications? Sad thing. OK, so this should go here, plus into a core feature request for notification templates ;).
Then this, or the breakpoint for deciding whether to notify now or later, should be configurable. Probably with two settings, one for "notify imemdiately for changes within the next n days" and one for "notify for all changes on the next day"
changed this line in version 5 of the diff
changed this line in version 5 of the diff
changed this line in version 5 of the diff
added 1 commit
Compare with previous version
https://edugit.org/AlekSIS/official/AlekSIS-Core/-/issues/659
Blocked by https://edugit.org/AlekSIS/official/AlekSIS-Core/-/merge_requests/983 ~"workflow::blocked"
\label ~"workflow::blocked"
mentioned in merge request AlekSIS-App-Untis!431
added 1 commit
Compare with previous version
added 3h of time spent
added 8 commits
masterCompare with previous version
added 2 commits
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 20m of time spent
added 3 commits
masterCompare with previous version
added 1 commit
Compare with previous version
added 1h of time spent
added 1 commit
Compare with previous version
resolved all threads
marked this merge request as ready
No newline at end of file
resolved all threads
changed this line in version 14 of the diff
added 13 commits
7aca0719- Write a change tracker and implement basic notifications for timetable changes31043aa6- Add tests for change tracker and notifications637d35d9- Don't send notifications for changes in irrelevant time ranged0b7fcaa- Add preferences for timetable change notifications9cf9fa33- Add mode for sending notifications for the next day473cef6d- Tidy notification and change tracker code3a28ee0b- Either directly send notifications or delay them for later640c12f7- Reformat4a5b7ad9- Fix notification testaf211f86- Update changelog0184f392- [Docs] Add information on how to use notifications for users547bc550- [Docs] Add information about setting up notifications in admin handbook1820081a- Depend on current Core to include scheduled notificationsCompare with previous version
mentioned in commit
6f667b881b