Skip to content

2023

Update

Improvements

  • ChronoLink now supports event reminders for Google and Microsoft.
    • Add the reminderset transformer to your connection configuration to use this feature. The new Reminders section of our User Guide has additional information.
  • Added ability to write "Out of Office" events to Google Calendar. This makes it possible to seamlessly synchronize vacations, holidays etc. with Microsoft calendars ("Show as: Away") in both directions.
    • To turn a regular event into an Out of Office event, add the statuschange transformer to your connection configuration.
    • Previously, Google did not offer a way for third-party applications to write such events; they could only be read. Recently, however, Google extended their API to cover this.

Update

Improvements

  • Google Calendar connections that fail for the reasons listed below are now marked as broken, displayed with an explosion icon (💥) and not retried until triggered manually.
    • ChronoLink permissions were revoked using Google's account settings page:
      To resume synchronization, log in to my.chronolink.app, then click the 🔄 icon for the respective linked account to re-authorize ChronoLink.
    • An organization administrator deleted your Google Workspace account:
      The deleted account prevents the ChronoLink settings page from working properly. Please contact ChronoLink support so we can unlink the Google Workspace account to restore ChronoLink functionality for your remaining accounts.

Update

Improvements

  • To create a ChronoLink account, new users now have to click one of the Sign up using Google or Sign up using Microsoft buttons. Also, ChronoLink now displays a success message after an account was created.
    • Previously, there were no separate "Sign up" buttons. When logging in using a new Google/Microsoft account, a new ChronoLink account was created automatically without asking or notifying the user.
  • When you add a linked account or add calendar access, ChronoLink now displays a success message on top of the settings page. Previously, it only silently jumped back to that page.

Update

Improvements

Update

Improvements

  • Connections that fail for non-temporary reasons are now marked as broken, displayed with an explosion icon (💥) and not retried until triggered manually.
    • Previously, ChronoLink did not distinguish permanent from temporary failures. Consequently, any failing connection would simply be marked as interrupted, displayed with a warning icon (⚠️) and retried within the next ten minutes. That behavior is now reserved for failures that are (likely to be) of temporary nature.
    • Later, we plan to add a feature that sends email notifications when a connection breaks this way.
  • Connections that use Outlook.com / Exchange Online calendars are now marked as broken when the authorization has been revoked.
    • According to Microsoft, authorization is revoked either when the user explicitly removed the app permission, or when their account password was changed.
    • In both cases, you can re-authorize ChronoLink by logging in to my.chronolink.app and clicking the 🔄 icon for the respective linked account.

Fixes

  • When you create or edit a connection, ChronoLink now checks immediately for the error cases listed below. Previously, the connection would be saved, but fail when run.
    • Invalid values for the duration condition, e.g. "30m" instead of the required "0:30".
    • Using the property condition without specifying key.

Update

Improvements

  • The time frame for past events can now be configured for each synchronization connection. Previously, all connections used the same starting date (2 weeks before you signed up).
    • If you are not interested in older events, you can edit your connections to shorten the time frame. Doing so can improve synchronization performance for calendars with many events.
    • Newly created connections default to 'today'.
  • ChronoLink now allows configuring a sliding window as the past event timeframe.
    • Use this to limit synchronization to current events, e.g. of the last two weeks. As time moves on, older events from the source calendar will automatically be cleaned up in the sink calendar.

Fixes

  • Deleting a connection or calendar access now requires a second click for confirmation.
    • This was always the intended behavior, but only worked properly in Firefox. Due to a bug in our code, the deletion happened immediately in Chrome and Chromium-based browsers.

Update

Fixes

  • When reading the "Location" field from a Microsoft calendar, ChronoLink no longer turns values like "Teams" into "Teams (, )".
    • This happened because of a bug in the code that turns a structured physical address into a single line of text such as "Joe's Grill (123 Main Road, Exampletown, Somestate, 9876, United States)".
  • Fixed a bug that prevented ChronoLink from ever clearing the "Location" field of events in a Microsoft calendar that were created by earlier runs.
    • This could happen e.g. when one added a { "type": "textchange", "field": "LOCATION", "mode": "CLEAR" } transformer to a connection after it had already run at least once.

Update

Fixes

  • Work log entries from Atlassian Jira that start at the same date/time are now synchronized correctly. Previously, ChronoLink only synchronized one of these entries and discarded the others.

Update

Improvements

  • ChronoLink now supports reading work log entries from Atlassian Jira.
    • This feature enables you to use your Google or Microsoft calendar to check which times you have logged work for. Seeing Jira work logs side by side with your meetings and other appointments (or time entries from Clockodo) can also make it really obvious for which times you still need to log work.
    • Note that ChronoLink only supports Jira Data Center or Jira Server. Support for Jira Cloud will likely be added later.
    • To use this, you will need to create a Personal Access Token for Jira. See the "Atlassian Jira" page in our user guide for details.

Update

Improvements

  • Connection runs are now scheduled exactly every 3 minutes. In the rare case that a connection run takes longer than 3 minutes, missed runs are skipped, but the next run will match the original schedule.
    • Previously, there was a three-minute delay between one run finishing and the next one starting.

Fixes

  • Events that start and end at the same date/time (i.e. which have a duration of 0 minutes) are now handled correctly by the time and duration conditions.
    • Previously, the time condition never matched such events. Worse, the duration condition would abort the connection run when encountering such an event.