#6612: Quire Feedback
Status: To-do
Assignees: Golda

With "Display completed tasks" enabled, every completed occurrence of a recurring task leaves an endless recurring event in Google Calendar. Each year (or month) adds one more copy of the same event.

Steps to reproduce

  1. Enable Google Calendar Instant Sync for a project with "Display completed tasks" checked.
  2. Create a yearly recurring task with a due date, e.g. Anna - birthday on 5 Nov.
  3. Complete it. Quire creates the next occurrence as a new task (#A → #B), as usual.
  4. Look at the following years in Google Calendar.

Expected: one event per date. The completed task keeps a single event on its own date, and only the active task repeats. Actual: the event of the completed task #A is still a recurring series with no end (RRULE without UNTIL/COUNT). The new task #B gets its own new series. From the next year on, both series show the same date, and each later completion adds another one.

Notes

  • In our birthdays calendar there are 19 duplicated dates this way, the nearest on 5 Nov 2026. In a monthly bills calendar three tasks (rent, gas, electricity) had two overlapping series each, so every month from Nov 2025 to Dec 2027 showed every bill twice (78 duplicate pairs).
  • It is not consistent. For some completed tasks the series is cut correctly, and in one case the completed occurrence disappeared from the calendar entirely although completed tasks should be shown.
  • With "Display completed tasks" off, the completed task's event is removed, so the problem is limited to calendars that show completed tasks. Turning the option off later does not clean up the old series.
  • Similar to the resolved Google Calendar Instant Sync is deep buggy for completed recurring tasks, but this happens on normal completion, without refreshing the sync.

Request: when a recurring task is completed and its next occurrence is created, end the completed task's series (UNTIL its own date, or make it a single event). Each occurrence is already its own task, so exporting it as a single event would avoid the overlap altogether.

Created by Grox Oct 31, 2026, Edited Nov 2, 2026