Harmonise
Browse documentation

Events and linked Tasks

Keep preparation work connected to an Event without turning it into part of the commitment.

Before you begin

  • A writable Event calendar

Linked Tasks are useful when work must be completed by an Event in your calendar.

For example, Project review is an Event because it happens at a set Date and Time. Prepare the figures is a Task because it is work that needs to be completed before the review.

Linking them keeps the preparation attached to the commitment without turning the Task into an Event.

What changes when a Task is linked?

The Event controls two Task details:

  • the Task uses the Event’s calendar; and
  • the Event supplies the Task’s effective deadline.

Every Event has one immutable IANA timezone. A new Task created from an Event uses the Event calendar and adopts the Event timezone. An existing Task can be linked or relinked only when it already uses the Event calendar, and the link operation aligns the Task timezone with the Event timezone.

For a timed Event, its start becomes the Task’s effective Due Date and Time. For a one-day all-day Event, its local Event date becomes the Task’s effective Due Date. For a multi-day all-day Event, its first local date becomes the Task’s effective Due Date. An all-day Event does not invent an exact deadline time.

The Task can still have its own:

  • title and description;
  • Scheduled Date or Scheduled Date and Time;
  • estimated duration;
  • Task reminders;
  • subtasks;
  • completion state; and
  • Task-owned temporal interpretation using its stored Task timezone.

The Event tells Harmonise when the work is due. The Task schedule tells Harmonise when you plan to do it. While the Event relationship controls the timezone, the linked Task does not expose an independently selectable timezone. Ordinary Event movement does not change the Event timezone. The Task still stores a Task timezone for its own temporal interpretation; it is aligned from the Event during linking or relinking.

A linked Event and Task example

Project review

  • Event Date and Time: Monday at 10:00-11:00 AM
  • Calendar: Work

Prepare the figures

  • Effective Due Date and Time: Monday at 10:00 AM
  • Scheduled Date and Time: Friday at 3:00-4:00 PM
  • Estimated duration: 60 minutes
  • Subtasks:
    • Check the latest figures
    • Update the charts
    • Send the draft

Add a Task to an Event

On mobile

  1. Create or edit the Event.
  2. Open the linked Tasks section.
  3. Add a new Task or choose an existing Task.
  4. Add the Task title and any useful Task-owned details.
  5. If the Event repeats, choose how broadly the Task should be attached.
  6. Save the Task changes, then save the Event.

On web

  1. Create or edit the Event.
  2. Open Tasks.
  3. Choose Add task.
  4. Enter the Task title and any useful Task details.
  5. If the Event repeats, choose how broadly the Task should be attached.
  6. Apply the Task changes, then save the Event.

A new Task created inside the Event composer uses the Event calendar automatically. An existing Task can be linked only when it already uses the Event calendar. Harmonise rejects a calendar mismatch instead of moving the Task automatically.

Choose which Events receive the Task

A one-time Event receives one linked Task. A recurring Event gives you three attachment choices.

This event only

Choose This event only when the Task belongs only to the selected Event.

  • Earlier Events do not receive the Task.
  • The selected Event receives the Task.
  • Later Events do not receive the Task.
  • The Task does not follow the Event series.

This and future events

Choose This and future events when the Task should begin with the selected Event and continue with later occurrences.

  • Earlier Events do not receive the Task.
  • The selected and eligible later Events receive the Task.
  • The Task repeats by following the Event.
  • The Task does not have its own Task repeat rule.

Entire series

Choose Entire series when the Task belongs to every eligible Event in the series.

  • Eligible earlier Events receive the Task.
  • The selected Event receives the Task.
  • Eligible future Events receive the Task.
  • Deleted, excluded, or otherwise nonexistent occurrences do not receive it.
  • The Task repeats by following the Event.

The difference is important: This and future events begins from the Event you selected, while Entire series also includes eligible earlier Events.

These choices control which Event occurrences receive the linked Task. They are separate from Event file attachments: Event attachments belong to the Event or recurring Event series and are shared by its occurrences.

When the Event moves

Moving the Event changes each linked Task’s effective deadline and recalculates eligible deadline reminders.

For a timed Event, the new Event start becomes the linked Task’s effective Due Date and Time. For an all-day Event, the new first local date becomes the linked Task’s effective Due Date.

The Task’s Scheduled Date or Scheduled Date and Time does not move automatically. Scheduled-start reminders remain tied to the Task’s existing timed schedule. A Task schedule is allowed to remain after the Event-controlled deadline. The frontend may show a non-blocking warning, but the state remains valid and saving is not blocked. Reschedule the Task only if you want the planned work to happen earlier.

When the Event calendar changes

A linked Task always uses the Event calendar. Changing the Event calendar updates eligible Tasks that remain linked to the affected Event or Event series, and aligns their stored Task timezone with the Event timezone.

Changing the Event calendar is different from moving the Event. Moving the Event does not change its immutable timezone; linking or relinking is when Harmonise aligns the linked Task timezone.

An eligible linked Task is one that still exists, remains linked, and belongs to an Event occurrence that still exists in the selected scope. Completion, customized Task details, subtasks, and a Task-owned schedule do not break that link.

Reminders and subtasks

Event reminders and Task reminders remain separate. An Event can have up to two active reminders. Each reminder is at the Event time or a supported non-negative offset before it; zero means the Event time or Event date, depending on the Event type. Moving the Event recalculates its Event reminders. A saved Event reminder is an alert, not an ordinary Inbox item.

A linked Task can use deadline reminders based on the Event-controlled effective deadline and scheduled-start reminders based on its own timed Scheduled Date and Time. Moving the Event updates eligible deadline reminders but does not move scheduled-start reminders.

For an all-day Event, the linked Task uses its effective date-only Due Date and the same date-only reminder policy as any other date-only Task. It does not invent a midnight delivery time.

Subtasks remain part of the Task. Changing the Event’s time, recurrence, or calendar does not rewrite the Task’s subtasks.

Completing a linked Task does not complete the Event. The Event also does not complete the Task automatically when its time passes.

Deleting the Task does not delete the Event.

Unlinking turns the Task into a standalone, non-recurring Task. It keeps its Task-owned details and preserves the former Event-controlled deadline as its own Due Date or Due Date and Time. It does not inherit the Event repeat rule, and no future Tasks are generated from the former relationship.

Delete the Event

Deleting an Event deletes only Tasks whose Event or Event-series link is still present when deletion begins. A detached or unlinked Task is standalone and remains.

  • Deleting one Event occurrence deletes every Task still linked to it.
  • Deleting This and following occurrences deletes still-linked Tasks in the selected and later affected range; earlier Events and linked Tasks remain.
  • Deleting the Entire series deletes every Task still linked through that Event-series relationship, including completed, historical, and customized Tasks.

The Event operation supports Only this occurrence, This and following occurrences, and Entire series. The current mobile and web deletion dialogs expose only Only this occurrence and Entire series, so the middle scope is not available from every platform or every Event. Editing scopes are separate and may still offer This and following occurrences when safe.

Task-owned schedules, reminders, subtasks, completion state, and exceptions are deleted with a still-linked Task. To retain a Task, unlink it before deleting the Event.

Review Event details

Select an Event from the calendar or Agenda to review its calendar, Event dates and times, immutable Event timezone, description, location, reminders, repeat information, linked Tasks, participants and RSVP state when available, online meeting, attachments, activity or update history, and any read-only or unsupported-recurrence warning.

On mobile, Event details open from the calendar and Edit event opens the full Event composer. On web, Event details open in an inspector and edits use the Event edit flow. The fields are not displayed identically on both platforms. Save or delete the Event only after linked Tasks finish loading so Harmonise knows which Tasks the change affects.

Review activity

Event details show saved activity when it is available. On mobile, open the Event updates screen to load the activity timeline for the selected Event. Refresh the Event details when you need the latest saved activity.

Saving linked Event changes

Some eligible core Event changes can be saved locally and synchronized later. This depends on whether Harmonise can save the Event locally, the Event’s calendar, the change being a supported Event-only change, and the absence of a conflict or other synchronization barrier. Linking Tasks, changing attachments, managed online meetings, invitations and RSVP side effects, and provider-owned changes can require a connection because they have server-owned side effects.

Common problems

The Task must already use the Event calendar. Harmonise does not move an existing Task to another calendar as part of linking.

The Task has the wrong effective deadline

For a timed Event, check the Event start. For an all-day Event, check its first local date. That is the Task’s effective deadline while the link remains.

The Task did not appear on earlier Events

Check the attachment choice:

  • This event only uses only the selected Event.
  • This and future events starts from the selected Event.
  • Entire series also includes eligible earlier Events.

The Task schedule did not move with the Event

That is expected. The Event changes the Task’s effective deadline, not its Scheduled Date or Scheduled Date and Time. A Task schedule after the Event-controlled deadline is valid. Harmonise may show a non-blocking warning, but saving is not blocked; reschedule or clear the Task schedule only if you want the planned work to happen earlier.

Completing the Task did not complete the Event

Tasks and Events keep separate completion behavior. Complete the Task when the work is finished; the Event remains a calendar commitment.

Next steps

Events

Create timed or all-day commitments, add useful details, and keep your calendar current.

Read guide

Timezones

Understand system and manual account timezones, fixed Event and Task zones, and date-only planning while travelling.

Read guide