394171 - Repeatings should be filterable by calendars or categories

Status: NEW

(Calendar :: General, enhancement)

Description

[Patrick Strasser]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Build Identifier: 

Often I create events that repeat for a long period of time (half a year), but which should not occur on certain days: holidays, vacation, if colliding with other more important events.
Currently I create the event with repeating and remove the colliding events afterwards.

It would be nice if one could specify something like "Repeat every week, but not if the day has an all-day event in calendar 'vacation'." or "Repeat only on days with events having category 'work'." Very fine would be to show candidate recurrences that match/match not the filter criteria to confirm the inclusion/exclusion.

An example: 
A course at the university, from October 1st until Feb. 3rd, but not on days from the calendars "local holidays" and "university vacation".
Doing this for 10 courses and say 8 days to cancel is really annoying.

Reproducible: Always

Comment 1

[Patrick Strasser]

With a "workday" or "holiday" calendar, bug 390620 could be tackled as well.

Comment 2

[Philipp Kewisch [:Fallen][📱📆]]

There is no automation for this in rfc2445. The exceptions would have to be set manually. I can imagine this is not trivial since the exceptions need to be kept in sync with the respective calendars. I do see the use for this and have thought about this myself as well.

Confirming bug, but I doubt it can be fixed in a near timeframe.

Comment 3

[Patrick Strasser]

I would not expect this to work dynamically. I'd expect to get an oportunity at creation of an repeating event to exclude certain repeatings according to some condition like stated above or "not on Sundays". 
If I'd change the event or re-check the event, I'd be able to trigger the exception-mechanism again. Otherwise it would be hard for me as user to register all changed events as they change, if such a dependency would be recalculated on every change of the dependent events.

A link or note on the exception-triggering event would be nice to have a record why this event was excepted. Of course this is eye-candy.