After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 739296 - Provide a way of creating/handling recurrent events
Provide a way of creating/handling recurrent events
Status: RESOLVED OBSOLETE
Product: gnome-calendar
Classification: Applications
Component: Edit dialog
unspecified
Other Linux
: Urgent enhancement
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
: 764950 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-10-28 13:11 UTC by Georges Basile Stavracas Neto
Modified: 2017-11-24 21:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot of Google Calendar's design (39.52 KB, image/png)
2016-12-18 13:49 UTC, Jean-François Fortin Tam
Details

Description Georges Basile Stavracas Neto 2014-10-28 13:11:18 UTC
When the event is recurrent, we actually have no clue of the in GNOME Calendar. The app should indicate that the event is recurrent by any means. The obvious option is to show an "Reload"-like icon before (or after) the event's name.
Comment 1 Luis Henrique Mello 2015-05-24 18:13:45 UTC
I was even wondering how to create a recurrent event in the 'new event' dialog, one that you can set to repeat on a daily/weekly/monthly/yearly base...
Comment 2 Erick Perez Castellanos 2015-05-24 21:27:00 UTC
(In reply to Luis Henrique Mello from comment #1)
> I was even wondering how to create a recurrent event in the 'new event'
> dialog, one that you can set to repeat on a daily/weekly/monthly/yearly
> base...

We're, certainly, missing that feature. Thanks for the report. I'll be changing the title of bug to reflect the actual feature.

(In reply to Georges Basile Stavracas Neto from comment #0)
> When the event is recurrent, we actually have no clue of the in GNOME
> Calendar. The app should indicate that the event is recurrent by any means.
> The obvious option is to show an "Reload"-like icon before (or after) the
> event's name.

I don't think we should reflect that on the event-widget. Yet we should discuss that.
Comment 3 Georges Basile Stavracas Neto 2015-05-24 21:31:00 UTC
This is an old bug description, and indeed I changed my mind about showing event recurrency at event-widget. It may be a bad idea.

We should as the designers for some feedback in here.
Comment 4 Luis Henrique Mello 2015-05-24 22:41:01 UTC
(In reply to Georges Basile Stavracas Neto from comment #3)
> This is an old bug description, and indeed I changed my mind about showing
> event recurrency at event-widget. It may be a bad idea.
> 
> We should as the designers for some feedback in here.

When you create or edit an event, there are widgets in the dialog box to configure when it starts and ends. Right below these there could be a 'Repeat periodically' checkbox and then you could set the period - daily, weekly, monthly, etc with another widget.
Comment 5 Erick Perez Castellanos 2016-04-12 16:14:13 UTC
*** Bug 764950 has been marked as a duplicate of this bug. ***
Comment 6 Jean-François Fortin Tam 2016-12-18 13:49:55 UTC
Created attachment 342163 [details]
screenshot of Google Calendar's design

It doesn't actually matter much to me that the event is indicated as recurrent within the month/week views... what matters is that I can create and edit it like a recurrent event.

Currently, if you have an existing recurrent event and you click it to make changes (ex: add a location), only the single occurrence gets changed instead of all the series.

When you do a change to a recurrent event, or quick-delete it, Google Calendar asks you if you want the change to apply to:

- Only this event
- Following events
- All events

They also provide explanatory text besides each choice button.
Comment 7 Georges Basile Stavracas Neto 2017-11-24 21:31:52 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/6.