There is a problem with usability on repeated events. The UI says that the event should be repeated and should "Stop repeating after # occurrences".

  • If you pick a negative number, you get an error as expected.
  • If you pick 0, you get an error, even though this would just mean, that the event would not repeat.
  • If you pick 1, the event won't be repeated. You'll just have that one event.
  • If you pick a bigger number (let's say 5), you get a total of five events.

The problem is that the count is the total count of events, and NOT the number of repetitions as the UI says. This confuses users and makes little sense. It's an off-by-one mistake...

It seems like the whole interface should be looked through, to check if the wording in general is correct for repetitions.

Comments

vorlon77’s picture

This is a common phrase for calendar programs and this should probably mean the same thing as it does on Google Calendar, MS Outlook, etc. It would be more confusing to users if something other than "after # occurrences" was used or if the number meant something different. So, if 3 was specified, then there should be a total of 3 events just like the UI says.

vorlon77’s picture

Issue summary: View changes

off-by-one

geek-merlin’s picture

Version: 7.x-2.5 » 7.x-2.x-dev
Priority: Major » Minor
Issue summary: View changes
Status: Needs work » Active

Adjusting prio and status.

Someone (tm) might add some phrases that other calendars use here.