Inform users if their CRUD actions result in overlapping absences & the consequences of that #35

New issue

Open

opened 2024-11-28 15:18:26 +01:00 by yuha · 1 comment

yuha commented

2024-11-28 15:18:26 +01:00

(Migrated from edugit.org)

The following discussion from !115 should be addressed:

@yuha started a discussion: (+2 comments)
@hansegucker @ZugBahnHof two questions:
1. We should probably inform the user in case of overlapping absences and the consequences of creating/editing an absence in a way that leads to overlaps (cuts to existing absences). How exactly should this happen? I'd think of something like the overview step when creating absences in the coursebook that shows which lessons will be affected.
2. This is more related to Alsijils use of Kolego absences, but how exactly should instances that relate to Kolego absences be updates in case these said absences change?

The following discussion from !115 should be addressed: - [ ] @yuha started a [discussion](https://edugit.org/AlekSIS/onboarding/AlekSIS-App-Kolego/-/merge_requests/52#note_100483): (+2 comments) > @hansegucker @ZugBahnHof two questions: > > 1. We should probably inform the user in case of overlapping absences and the consequences of creating/editing an absence in a way that leads to overlaps (cuts to existing absences). How exactly should this happen? I'd think of something like the overview step when creating absences in the coursebook that shows which lessons will be affected. > 2. This is more related to Alsijils use of Kolego absences, but how exactly should instances that relate to Kolego absences be updates in case these said absences change?

Rows
Columns