Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advanced calendar event repeat rules #1666

Open
1 of 2 tasks
Tracked by #2196
charlag opened this issue Dec 6, 2019 · 7 comments
Open
1 of 2 tasks
Tracked by #2196

Advanced calendar event repeat rules #1666

charlag opened this issue Dec 6, 2019 · 7 comments
Labels
goal: best calendar app roadmap label to indicate that this issue is/was part of the roadmap and is visible on the website
Milestone

Comments

@charlag
Copy link
Contributor

charlag commented Dec 6, 2019

As a user i want to be able to define more advanced repeat rules so that i can be more flexible with defining repeating events.

Acceptance critera

  • Allow configure rules for a certain day (e.g. BYMONTHDAY=22, BYDAY, )
  • Exception for repeating events (EXDATE)

Implementation hint

We should support BY* repeat rules for the calendar events like BYMONTH/BYDAY etc to enable things like "every second Tuesday each month".

see https://tools.ietf.org/html/rfc5545#section-3.3.10

examples are:

BEGIN:VCALENDAR
PRODID:-//company//calendar app//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:byruletes
X-WR-TIMEZONE:Europe/Berlin
BEGIN:VEVENT
DTSTART;VALUE=DATE:20200622
DTEND;VALUE=DATE:20200623
RRULE:FREQ=MONTHLY;BYMONTHDAY=22
DTSTAMP:20200624T071758Z
UID:XXX0
CREATED:20200622T083746Z
DESCRIPTION:
LAST-MODIFIED:20200622T083746Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:on 22nd monthly
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20200622
DTEND;VALUE=DATE:20200623
RRULE:FREQ=MONTHLY;BYDAY=4MO
DTSTAMP:20200624T071758Z
UID:XXX2
CREATED:20200622T083804Z
DESCRIPTION:
LAST-MODIFIED:20200622T083814Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:fourth monday
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20200624
DTEND;VALUE=DATE:20200625
RRULE:FREQ=WEEKLY;WKST=MO;BYDAY=MO,WE
DTSTAMP:20200624T071758Z
UID:XXX2
CREATED:20200624T071724Z
DESCRIPTION:
LAST-MODIFIED:20200624T071724Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:monday and wednesday
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR

event which starts on 22nd each month
event which happens every 4th Monday and Wednesday
event which happens every Monday and Wednesday

@charlag charlag added the improvement nice-to-haves that are not impeding usage of any features label Dec 6, 2019
@charlag charlag added this to the Roadmap milestone Dec 6, 2019
@charlag charlag added this to To do in Calendar out of beta via automation Dec 6, 2019
@joshuaobrien
Copy link
Contributor

I am really interested in having this feature. I am happy to dedicate some time each day to working on this, if you are interested in additional hands!

@charlag
Copy link
Contributor Author

charlag commented Dec 9, 2019

@joshuaobrien that's nice to hear!
You could start with an algorithm, you cannot really change database type but you could prototype it.
See the spec I linked and CalendarModel

@armhub armhub modified the milestones: Roadmap, Small improvements May 18, 2020
charlag added a commit that referenced this issue Jul 8, 2020
Co-authored-by: LordStriller <LordStriller@users.noreply.github.com>
@bedhub bedhub added the small improvement A small improvement which can hopefully be implemented within a short time frame. label Mar 17, 2021
@bedhub bedhub modified the milestones: Small improvements, Roadmap Mar 17, 2021
@bedhub bedhub removed the small improvement A small improvement which can hopefully be implemented within a short time frame. label Mar 17, 2021
@vaf-hub
Copy link
Contributor

vaf-hub commented Sep 1, 2021

We should also allow to modify single events that are part of a series, such as changing the description only for one event and not for the other occurrences.

@bedhub bedhub mentioned this issue Sep 1, 2021
15 tasks
@bedhub bedhub added new feature user stories in varying refinement states idea notes down not immediately solvable things that don't have general buy-in yet and removed improvement nice-to-haves that are not impeding usage of any features idea notes down not immediately solvable things that don't have general buy-in yet labels Feb 4, 2022
@BiancaMass
Copy link

We should also allow to modify single events that are part of a series, such as changing the description only for one event and not for the other occurrences.

On that: would be great to have the possibility to delete or change the date for a single even of a series i.e. giving the options of "edit this event only" or "edit all events of the series" when making changes to a particular event.

@jacamporaGIS
Copy link

We should also allow to modify single events that are part of a series, such as changing the description only for one event and not for the other occurrences.

On that: would be great to have the possibility to delete or change the date for a single even of a series i.e. giving the options of "edit this event only" or "edit all events of the series" when making changes to a particular event.

yes this is really important

@jacamporaGIS
Copy link

I would also like to be able to easily copy events to other days. lets say i work the same shift 3 nights a week, I could just copy it from monday to wednesday

@bedhub bedhub added goal: best calendar app roadmap label to indicate that this issue is/was part of the roadmap and is visible on the website and removed new feature user stories in varying refinement states labels Feb 2, 2024
@SjoerdV
Copy link

SjoerdV commented Apr 4, 2024

Just adding some search terms to this issue as 'repeating' might be missed by some:
advanced recurring event
advanced recurring schedule
complex recurrence pattern

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
goal: best calendar app roadmap label to indicate that this issue is/was part of the roadmap and is visible on the website
Projects
Development

No branches or pull requests

8 participants