Content
View differences
Updated by Oliver Günther over 1 year ago
### Steps to reproduce
1. Create a meeting series that starts tomorrow 10 AM
2. Finish the template so that tomorrow 10 AM meeting is open
3. On the series show page, click more menu -> edit series
4. Reschedule the series to 9 AM
### What is the buggy behavior?
_Please describe the bug in as much detail as possible. Example:_
* You now have two open meetings, one for the old, one for the new time
* If you export this ICS, it will contain the two meetings with invalid RECURRENCE-ID, which will cause errors in groupwares, at least mailbox.org
### What is the expected behavior?
_Describe how the application should behave like. Example:_
1. All _n_ open meetings in the future will be rescheduled:
1. **If only the start time (hours) changed:** simply update the start time hour of the instantiated meeting to match the new time
2. **If the date/frequency/interval, etc has changed:** according ot the next _n_ planned meetings according to the new series schedule. Even if moving from daily to monthly, or weekly to daily. Any cancelled meetings will be removed
2. If the user changes the # occurences so that it's fewer than actual open occurences, then you get an inline validation in the meeting details dialog.
###
1. Create a meeting series that starts tomorrow 10 AM
2. Finish the template so that tomorrow 10 AM meeting is open
3. On the series show page, click more menu -> edit series
4. Reschedule the series to 9 AM
### What is the buggy behavior?
_Please describe the bug in as much detail as possible. Example:_
* You now have two open meetings, one for the old, one for the new time
* If you export this ICS, it will contain the two meetings with invalid RECURRENCE-ID, which will cause errors in groupwares, at least mailbox.org
### What is the expected behavior?
_Describe how the application should behave like. Example:_
1. All _n_ open meetings in the future will be rescheduled:
1. **If only the start time (hours) changed:** simply update the start time hour of the instantiated meeting to match the new time
2. **If the date/frequency/interval, etc has changed:** according ot the next _n_ planned meetings according to the new series schedule. Even if moving from daily to monthly, or weekly to daily. Any cancelled meetings will be removed
2. If the user changes the # occurences so that it's fewer than actual open occurences, then you get an inline validation in the meeting details dialog.
###