GNOME Bugzilla – Bug 314599
Recurrence Tab Should Not Default To Forever
Last modified: 2011-09-27 10:46:50 UTC
When you are creating a new meeting and select the option to make it a recurrence meeting, the default is to create appointments out forever. Please, that really needs to get changed. That is just completely dangerous in the number of appointments it will send to the other people (and possibly through the GW POA). Default should be Every 1 Day for 1 Occurrence and then let the user change it from there. Other information:
Confirming it. Should be a easy_fix.
Committed the fix to gnome-2-12 and head branches.
Verified in evolution 2.4.1
I would argue that most recurring items don't have a fixed ending date and thus it is cumbersome to create them (https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/204582). I can see how this creates problems when teams are involved. But can we please try to find something that fits a broader set of requirements? IMHO, the correct fix would be to send out only a single mail for recurring items instead of the current solution of defaulting to a single occurrence (that is not recurring!) Reopening for discussion
Agree with Rolf. The first time I set a recurring event, I did not notice that it was defaulting to 1 occurrence. When I went back to edit the event, it led to another bug in Evolution, where editing a recurring event corrupts the calendar. See: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/362318 and http://bugzilla.gnome.org/show_bug.cgi?id=581688 I don't know what the default behavior should be, but IMO it should NOT be 1 occurrence. How could a recurring event only happen once? The default should be at least twice, so that we aren't breaking the laws of language.
I would not have any problem with the default being 2, or even 10. The issue we had with it going out forever is that with an enterprise backend like Groupwise it as churning out tons of meetings. The users then get one meeting for each occurrence date...possibly 100s of them at a time. This is nearly identical to the issue of the GNOME workspace switcher defaulting to "1" when you add it to your Panel. :) If the person is using the feature, for sure 1 is not what they will pick. So "2" sounds great to me.
Created commit 135b147 in evo master (2.27.6+) OK, defaulting to 2 now, but you can change in with a hidden int option: /apps/evolution/calendar/other/def_recur_count anything greater than zero is accepted.
Milan, thank you for working on this. Am I right to assume that the current implementation does allow the user to specify "forever" as default in his personal configuration?
(In reply to comment #8) > Am I right to assume that the current implementation does allow the user to > specify "forever" as default in his personal configuration? Nope, the only thing you can specify is count of default occurrences. It will be always "for X occurrences". Though might make sense to have some special value, large enough, to switch to "forever". What do you suggest? Something like -1 for forever?
-1 for forever would be lovely? Should this ticket be reopened to track progress?
-1 for forever would be lovely. Should this ticket be reopened to track progress?
Created commit 80374b7 in evo master (2.27.6+) Recognizes -1 as forever. I added also a schema key definition for a GConf.
I'm running 2.28.3 in lucid and the default is 2, not -1. Reopening.
Yes, the default left on 2, but as noted in comment #7 you can change it in: /apps/evolution/calendar/other/def_recur_count and as noted in comment #12 a special value -1 can be used as well here. Thus just change it base don your needs. $ gconftool-2 --set --type=int -- \ /apps/evolution/calendar/other/def_recur_count -1