Reimplement notification system on base of new calendar system #209

New issue

Closed

opened 2023-07-18 21:25:55 +02:00 by hansegucker · 11 comments

hansegucker commented 2023-07-18 21:25:55 +02:00

Owner

Copy link

Possible Triggers:

• Lesson event created (e. g. extra lesson, event, whatever → regular lessons have to be excluded)
• Lesson event changed (⬆️)
• Lesson event deleted (⬆️)
• Lesson event created which amends something (e. g. substitution, supervision substitution)
• Lesson event changed which amends something (⬆️)
• Lesson event deleted which amended something (⬆️)

This ultimately leads to track all LessonEvent stuff and exclude those events which represent regular lessons.

Alarms shall be created if

• a new extra lesson, event, substitution, supervision substitution whatever is created (no earlier than a certain point x before this event → create alarm)
• one of those events changed (only if initial notification has been sent, otherwise initial alarm has to be updated)
• one of those events was deleted (only if initial notification has been sent, otherwise initial alarm has to be deleted)

The notification system for calendar events should depend on VALARM entries.

The calendar event should have some kind of API for custom notifications where Chronos can add some extra logic for the alarms.

Possible Triggers: - Lesson event created (e. g. extra lesson, event, whatever → regular lessons have to be excluded) - Lesson event changed (:arrow_up:) - Lesson event deleted (:arrow_up:) - Lesson event created which amends something (e. g. substitution, supervision substitution) - Lesson event changed which amends something (:arrow_up:) - Lesson event deleted which amended something (:arrow_up:) This ultimately leads to track all LessonEvent stuff and exclude those events which represent regular lessons. Alarms shall be created if - a new extra lesson, event, substitution, supervision substitution whatever is created (no earlier than a certain point x before this event → create alarm) - one of those events changed (only if initial notification has been sent, otherwise initial alarm has to be updated) - one of those events was deleted (only if initial notification has been sent, otherwise initial alarm has to be deleted) The notification system for calendar events should depend on `VALARM` entries. The calendar event should have some kind of API for custom notifications where Chronos can add some extra logic for the alarms.

hansegucker commented 2023-07-18 21:26:10 +02:00

Author

Owner

Copy link

mentioned in issue AlekSIS#58

mentioned in issue AlekSIS#58

yuha commented 2023-09-25 15:38:59 +02:00

Member

Copy link

mentioned in issue #214

mentioned in issue #214

yuha commented 2023-11-02 12:50:58 +01:00

Member

Copy link

mentioned in issue #223

mentioned in issue #223

hansegucker commented 2024-05-14 16:16:19 +02:00

Author

Owner

Copy link

changed the description

changed the description

hansegucker commented 2024-07-04 17:11:27 +02:00

Author

Owner

Copy link

changed the description

changed the description

hansegucker commented 2024-07-04 17:11:58 +02:00

Author

Owner

Copy link


yuha commented 2024-07-04 17:41:45 +02:00

Member

Copy link

assigned to @yuha

assigned to @yuha

yuha commented 2024-07-12 13:36:16 +02:00

Member

Copy link

needs https://edugit.org/AlekSIS/official/AlekSIS-Core/-/merge_requests/1523

needs https://edugit.org/AlekSIS/official/AlekSIS-Core/-/merge_requests/1523

yuha commented 2024-08-03 15:44:07 +02:00

Member

Copy link

created branch 209-reimplement-notification-system-on-base-of-new-calendar-system to address this issue

created branch [`209-reimplement-notification-system-on-base-of-new-calendar-system`](/AlekSIS/official/AlekSIS-App-Chronos/-/compare/master...209-reimplement-notification-system-on-base-of-new-calendar-system) to address this issue

yuha commented 2024-08-03 15:44:14 +02:00

Member

Copy link

mentioned in merge request !664

mentioned in merge request !664

hansegucker closed this issue 2024-12-23 12:55:49 +01:00

hansegucker commented 2024-12-30 11:06:13 +01:00

Author

Owner

Copy link

mentioned in commit d27dc18e95

mentioned in commit d27dc18e95b74453733ab94dc6730d82db992c96

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

797-add-getobjectsforperson

weblate-frontend

weblate

304-adapt-to-core-changes-of-calendaralarm-inheritance-structure

299-automated-substitution-list-doesn-t-correctly-consider-kolego-absences-with-start-end-dates

check/update-builddeps-package-json

check/update-eslint-rc-js

check/update-tox-ini

247-use-lessonevent-feed-for-aggregated-availability-feed

292-adapt-to-places

stable/4.0.0

281-add-argument-to-lesson-events-get_objects-method-that-bypasses-the-filtering-done-if-own-false

release/4.0.0.dev9

release/4.0.0.dev7

fss-test-substitutions

221-show-course-name-of-lessons-in-the-timetable

241-substitution-planning-cancelled-checkbox-does-not-have-false-as-value-when-unchecked-actively

242-add-query-for-groups-of-which-the-current-user-can-see-the-respective-timetable

234-add-links-to-different-timetables-in-timetable-details-cards

migration-for-legacy

228-drop-legacy-model-and-form-extensions

engs-4.0

211-implement-vue-substitution-frontend-2

204-graphql-schema-for-subject

engs

197-adaptations-for-spa-operation

175-graphql-schemas

rename-ugettext

feature/vuetify

i10n-ru-ua

161-manage-basic-data-in-frontend

40-personal-timetable-as-ics

add-docs

core-284-unify-permission-names

162-extend-the-reference-to-the-next-lesson

160-ignore-subject-color-in-timetable-if-fg-bg

trademark-hint

update/tox-makemessages

create-timeperiods

backup-signals

140-show-abbreviations-in-the-substitution-plan-only-once

144-preference-section-is-called-chronos

update/poetry-4

130-show-print-timetable-button-on-mobile-devices

update-poetry-lock

117-use-django-guardian-s-prefetch-mechanism-for-object-permissions

trigger-dist-pipeline

2.0a4

update-lockfile-core

gettext-lazy

update-tox2

update-tox

feature/use-entrypoints

core-317-separate-core-and-default-distribution

update-lock-file

fix-docker-build

fix/fix-import

update-poetry-lockfile

core-158-documentation-needed-for-first-release

87-make-chronos-work-with-current-core

group-subject

bugfix/affected-teachers-in-header-box-shown-multiple-times

licence-information

day-names

merge

file-refs

school-apps

core-116-migrate-to-material-design-icons

36-room-management

issue34

94-use-btn-dark-everywhere

sqloptimise

issue12

lessons_day

issue19

6.1.0

6.0.0

5.0.1

5.0.0

5.0.0b0

4.0.1

4.0.0

4.0.0.dev10

4.0.0.dev9

4.0.0.dev8

4.0.0.dev7

4.0.0.dev6

4.0.0.dev5

4.0.0.dev4

4.0.0.dev3

4.0.0.dev2

4.0.0.dev0

3.0.2

3.0.1

3.0

3.0b0

3.0.dev1

2.5

2.4.2

2.4.1

3.0.dev0

2.4

2.3

2.2.1

2.2

2.1

2.1dev3

2.1.dev2

2.1.dev1

2.1.dev0

2.0

2.0rc3

2.0rc2

2.0rc1

2.0b2

2.0b1

2.0b0

2.0a3

2.0a2

delete-tag

2.0a1

1.0a3

1.0a2

1.0a1

1.0a0

Labels

Clear labels   

Security

  

TeX

Needs LaTeX template

  

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

Backend (view code, models, logic, etc.)

  

part

ci

  

part

docs

Issue or addition to the documentation

  

part

frontend

Frontend (templates, etc.)

  

part

i18n

Translation or internationalisation issue

  

part

non-technical

Non-technical (policy, maintenance, etc.) issue or discussion

  

part

packaging

Issue concerning the packaging of AlekSIS and components

  

prio

1

Priority High

  

prio

2

Priority Medium

  

prio

3

Priority Low

  

release-mr-5.x

  

size

large

  

size

medium

  

size

small

  

source

customer

Requested by a customer or affiliated user

  

source

customer::fsmw

  

source

customer::fss

  

source

customer::teckids

  

source

downstream

Issue or merge request from other projects using AlekSIS or parts of it

  

type

breaking

  

type

bug

Bug

  

type

feature

New feature

  

type

refactoring

  

workflow

blocked

Issue is blocked by another issue

  

workflow

confirmed

The bug is reproducible and will be fixed

  

workflow

current-todo

  

workflow

discussing

Needs to be discussed before implementation

  

workflow

new-app

Requires new AlekSIS app, which has to be created

  

workflow

wontfix

The bug is not reproducible or the feature was decided against

  

source::aleksolotl

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

source::aleksolotl

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

yuha

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

aleksis/AlekSIS-App-Chronos#209

No description provided.