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

special dialog when editing repeating events [$120] #7

Open
georgehrke opened this issue Sep 17, 2016 · 42 comments

Comments

@georgehrke
Copy link
Member

commented Sep 17, 2016

When editing a repeating event the calendar needs a special dialog:

Do you want to change only this or this and all upcoming occurrences?


There is a $120 open bounty on this issue. Add to the bounty at Bountysource.

@georgehrke georgehrke added this to the 1.6-next milestone Sep 17, 2016

@georgehrke georgehrke changed the title special dialog when exigent repeating events special dialog when editing repeating events Sep 18, 2016

@georgehrke

This comment has been minimized.

Copy link
Member Author

commented Jan 19, 2017

requires #142 to be fixed

@bohni

This comment has been minimized.

Copy link

commented Jan 30, 2017

There should be three possibilities:

  • Only this event (eg. delete/change)
  • This and all upcoming events (eg. delete/change)
  • All events (eg. typo in title),
@georgehrke

This comment has been minimized.

Copy link
Member Author

commented Jan 30, 2017

I honestly don't see a need for three options. The two mentioned in the description should be just fine.

All events (eg. typo in title),

You usually don't spot a typo in a title 3 month after creating it. You will most certainly spot it right after creating the event.
Editing past events happens very very rarely. Ordinary users probably never change past events.

The ordinary use cases here are:

  • location changes for one or all future occurrences. You wouldn't change the location for past events, because they already took place.
  • same goes for additional attendees. New attendees for one or all future occurrences didn't attend the previous events, so why add them?
  • deleting one or all future occurrences. The past ones still took place, so why remove them?

Having two or three buttons is a big difference from a usability point of view. The user has more input to parse. It clutters the interface and makes it less intuitive to use.

Would be good to get more input here. @nextcloud/calendar @jancborchardt @eppfel

@claell

This comment has been minimized.

Copy link

commented Jan 30, 2017

To me it seems strange to not have the option to change all events, although it might not be necessary.

Regarding typos: There can also be ones spotted some time after creation.

@raimund-schluessler

This comment has been minimized.

Copy link
Member

commented Jan 30, 2017

Just for the record, Thunderbird gives

  • Edit just this occurrence
  • Edit all occurrences

However, I would show

  • Edit just this occurrence
  • Edit all future occurrences

And if 'now' is given by the selected event, you could still edit past events by navigating to the first occurrence and edit this one with 'all future occurrences' which would lead to effectively editing all occurrences.

@heikojansen

This comment has been minimized.

Copy link

commented Jan 30, 2017

Both Google Calendar and Novell GroupWise offer all three options (with GCal apparently resetting prior modifications to other events if "edit all events" is selected).

@bohni

This comment has been minimized.

Copy link

commented Jan 31, 2017

Lotus Notes even has 4 options:

  • Only this entry
  • All Entries
  • This and all previous entries
  • This and all future entries

And I would like to have the possibility to delete all entries, whether or not they took place.

@georgehrke

This comment has been minimized.

Copy link
Member Author

commented Jan 31, 2017

This and all previous entries

Seems like Lotus Notes is still stuck on the first revision of the icalendar standard 🙈
I can't think of any legitimate use case for that.

@bohni

This comment has been minimized.

Copy link

commented Jan 31, 2017

I know (http://dreckstool.de/hitlist.do), that's because I first wrote about three options. And still will vote for 3 options... :-)

@github-user-1

This comment has been minimized.

Copy link

commented Jan 31, 2017

I opt for three options - a) this event, b) all future events, and c) all events. This is how it also done by Google-Calendar which is used by millions of people and seems to be the right way in my viewpoint to offer changes for recurring events.

@skjnldsv

This comment has been minimized.

Copy link
Member

commented Jan 31, 2017

I won't mind three options imho.
But I also agree with @georgehrke pov. Too much information isn't suitable. But I could also see some uses for me that would require editing passed events too :/

@georgehrke

This comment has been minimized.

Copy link
Member Author

commented Apr 7, 2017

Reminder to myself:

  • don't use RECURRENCE-ID;RANGE=THISANDFUTURE. Support of most clients is very poor for this.
  • split up event and set UNTIL on old event instead.

macOS and iOS don't support RANGE=THISANDFUTURE. According to http://stackoverflow.com/a/30343374 Google calendar does neither.

Looking at the code, lightning should actually support RANGE=THISANDFUTURE, but will work fine with splitting the event up too.
lightning (on macOS) supports it neither

@georgehrke

This comment has been minimized.

Copy link
Member Author

commented Apr 7, 2017

requires #413

@strk

This comment has been minimized.

Copy link

commented May 4, 2017

#413 was merged, so this is open for work shall anyone want to help :)

@dehart

This comment has been minimized.

Copy link

commented May 4, 2017

Be aware that when attendees are invited to the event they get 2 emails

  • an update: the current event is ending
  • an invite: new series that has started.

Range property solves this but these are my test results:

Sad but true
Test file:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//GEDIT//NONSGML Version 1//EN
BEGIN:VEVENT
UID:1337-range-test@michael
DTSTART;VALUE=DATE:20170501
DURATION:P1D
DTSTAMP:20170401T160000Z
RRULE:FREQ=WEEKLY
STATUS:CONFIRMED
SUMMARY:Range-test: Weekly
END:VEVENT
BEGIN:VEVENT
UID:1337-range-test@michael
RECURRENCE-ID;RANGE=THISANDFUTURE;VALUE=DATE:20170605
DTSTART;VALUE=DATE:20170605
DURATION:P1D
DTSTAMP:20170401T160000Z
SUMMARY:Range-test: Changed
END:VEVENT
END:VCALENDAR

@georgehrke

This comment has been minimized.

Copy link
Member Author

commented May 4, 2017

@dehart As I said just two comments above, let's not use range, just split up and set until on the first one. ;)

#7 (comment)

@nshtg

This comment has been minimized.

Copy link

commented Apr 11, 2018

Any ETA on a stable release with this? Quite important feature!

@jospoortvliet jospoortvliet changed the title special dialog when editing repeating events special dialog when editing repeating events [$75] Aug 23, 2018

@jospoortvliet jospoortvliet changed the title special dialog when editing repeating events [$75] special dialog when editing repeating events [$80] Aug 26, 2018

@georgehrke georgehrke modified the milestones: 1.6.2, 2.0.0 beta2 Sep 8, 2018

@jospoortvliet jospoortvliet changed the title special dialog when editing repeating events [$80] special dialog when editing repeating events [$85] Sep 21, 2018

@jospoortvliet jospoortvliet changed the title special dialog when editing repeating events [$85] special dialog when editing repeating events [$90] Sep 30, 2018

@RDominique

This comment has been minimized.

Copy link

commented Sep 30, 2018

I just raised the bounty whith $5. Thanks to jospoortvliet to notice it and to change the description ;-)

I would like to propose that in order for someone to collect this bounty, that deleting 'this event only' also should work. Ref #7 (comment)

(It's a big issue with our family calendar... My wife is really bugging me about this :-/ )

@georgehrke georgehrke modified the milestones: 2.0.0 beta2, 2.2.0 Nov 5, 2018

@eppfel eppfel changed the title special dialog when editing repeating events [$90] special dialog when editing repeating events [$95] Jan 22, 2019

@stephenkilpatrick

This comment has been minimized.

Copy link

commented Feb 21, 2019

Added $25 to the bounty. This issue is rarely a problem for me, but when it is, it’s a big one.

@Tokowo

This comment was marked as off-topic.

Copy link

commented Mar 18, 2019

This still an issue, this is really annoying!

@jospoortvliet jospoortvliet changed the title special dialog when editing repeating events [$95] special dialog when editing repeating events [$120] Mar 26, 2019

@scroom

This comment has been minimized.

Copy link

commented May 7, 2019

I just raised the bounty with $25.

@Tokowo

This comment was marked as off-topic.

Copy link

commented May 7, 2019

This still an issue, this is really annoying!

Why my comment is mark as spam, this is still an issue and not a litlle one!

@karloluiten

This comment was marked as off-topic.

Copy link

commented May 7, 2019

Stop replying with "me too" replies (@Tokowo ). The issue is still open, meaning the issue still exists. If you have no new info to add, do not comment. If you want to speed up the process, add some $ to the bounty.
[ See reply of @georgehrke below ]

@georgehrke

This comment was marked as off-topic.

Copy link
Member Author

commented May 7, 2019

Why my comment is mark as spam, this is still an issue and not a litlle one!

Because your comment is not helping us move this issue further ahead. If you want to show your support for this ticket, use Github Reactions.

If you have any technical comments on the implementation, please comment.

If you just want to comment how badly you need this feature, please don't. It's just unnecessarily notifying everyone subscribed to this issue.

@Tokowo

This comment was marked as off-topic.

Copy link

commented May 7, 2019

I agree my comment it is not warm as a sunbeam! I'm sorry for that!
Well I did this comment because, this issue is open since 2016 and 3 years later, it still an issue without any progress, that's seam to be a forget dead end...
Mark my coment as a spam is rude and it is not helping too.
If you do answering to peoples by "marking as a spam" do not push anyone to invest in the bounty.

@torpak

This comment was marked as off-topic.

Copy link

commented May 7, 2019

@Tokowo
I would have written this directly to you, and only to you, but i could not, since you don't have a repository and your profile doesn't list a mail address.
Since you are not doing any of the things @georgehrke listed, you comment is just noise (or spam), annoying the developers who have no obligation to you what so ever and might reconsider working on this project altogether if they are annoyed enough.
The other group of people you annoy are the 58 people, who want this feature just as badly as you do, because you just potentially reduced their chances of ever getting this feature by just making noise,
to which i, sadly just added.
So please reconsider you attitude towards people who work in their free time on software that is obviously important to you.

@tcitworld

This comment has been minimized.

Copy link
Member

commented May 7, 2019

People, please stop replying to off-topic messages or we'll have to lock the issue.

@dbadura

This comment has been minimized.

Copy link

commented May 7, 2019

Will it be fixed in vue.js version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.