Skip to content

News

Update

Website Update

  • We have officially published our Terms of Service. Complementing our existing Privacy Policy, these terms formally describe our relations with users. As such legal matters are often boring, we did our best to keep the document short and easy to understand.

Update

Improvements

  • In addition to standard event fields like title or description, the text condition can now also be used to search properties.
    • This allows selecting (or omitting) events based on things like the name of the project a Jira worklog entry belongs to, or a vendor-specific iCalendar field.

Update

Fixes

  • When using our Outlook add-in to connect to Microsoft Exchange Server, the Outlook UI no longer becomes unresponsive for several seconds during sync connection runs.

    • The bug is present in all previous versions, but is more easily noticeable with 1.3.0.
    • Users of Exchange Online and Outlook.com were not affected as ChronoLink accesses those calendars via the cloud-based Microsoft Graph API.

    Setup

    Existing users need to install version 1.3.1 of ChronoLink Connector for Outlook. The installer will upgrade the existing installation.

    For general setup instructions, read the "Exchange Server" page of our user guide.

Update

Improvements

  • We released a new version of our Outlook add-in to connect to Microsoft Exchange Server. It features the following enhancements:

    • The add-in will now automatically recover from losing the connection to the ChronoLink servers (e.g. when the user connects to a VPN). Previously, the add-in remained inactive until the user quit and restarted Outlook.
    • Improved performance during startup to avoid Outlook automatically disabling the add-in.

    Setup

    Existing users need to install version 1.3.0 of ChronoLink Connector for Outlook. The installer will upgrade the existing installation.

    For general setup instructions, read the "Exchange Server" page of our user guide.

Update

Improvements

  • Added two features which can be used to simplify condition & transformer configuration in some cases:
    • The new unless transformer is a compact alternative to using if with a not condition.
    • The not condition now supports specifying a list of conditions via anyOf, which achieves the same result as specifying that list inside a nested or condition.

Update

Fixes

  • When synchronising work logs from Atlassian Jira, ChronoLink no longer seems to randomly ignore certain issues.
    • It turned out that when an issue has more than 100 worklogs, it cannot be found reliably with search criteria involving the worklogAuthor or worklogDate fields. The reason is a limitation that Atlassian had to put in to ensure good search performance.
    • To fix this, we have switched to another approach that no longer relies on those fields. As a side effect, this new approach also improves performance.

Website Update

Update

Improvements

  • Added the relativerange condition to select events based on the current time.
    • For example, this allows restricting synchronization to "current week", to "events remaining today" or to "the last 12 hours plus the next 24 hours". This way, synchronized events in the target calendar that are no longer in that time frame will be deleted automatically.
    • Combined with the if transformer, it could also be used to remove sensitive details from events until they have passed, or to highlight events that are currently running (e.g. add a ⭐ to the title and/or set a special color).
    • This complements various existing options related to date and time, such as:
      • The daterange condition where you set specific start/end dates
      • The time condition for day-of-week and time-of-day rules like "Wednesday between 9 and 12"
      • The duration condition which matches events of a certain (minimum/maximum) duration
      • The connection-level setting for synchronization time frame with predefined options like today, 2 weeks, 1 month, 3 months, 6 months and so on

Update

Fixes

  • When using our Outlook add-in to connect to Microsoft Exchange Server, ChronoLink no longer fails when encountering multiple accounts.

    • Users of Exchange Online and Outlook.com were not affected as ChronoLink accesses those calendars via the cloud-based Microsoft Graph API.

    Setup

    Existing users need to install version 1.2.0 of ChronoLink Connector for Outlook. The installer will upgrade the existing installation.

    For general setup instructions, read the "Exchange Server" page of our user guide.

Update

Improvements

  • When using Microsoft Exchange Server, ChronoLink now also synchronizes the visibility and status fields.

    • When synchronizing to Outlook.com or Exchange Online, the values for both fields will be kept. When the target is a Google calendar, ChronoLink will translate the values to their closest equivalent. For details, see the "Status" and "Visibility" tables in our docs.
    • Use the status and visibility conditions to select which events to (not) synchronize, and alter the field values using the statuschange and visibilitychange transformers.

    Setup

    Existing users need to install version 1.1.0 of ChronoLink Connector for Outlook. The installer will upgrade the existing installation.

    For general setup instructions, read the "Exchange Server" page of our user guide.

Fixes

  • Reverted most of the update interval change for iCalendar (ICS) feeds.
    • It turns out that most feeds used by our beta testers set the update interval way too high. For example, having a feed about table reservations only update once per day defeats the purpose of having the feed in the first place.
    • As a quick fix, we reverted our iCalendar code to the old behavior for all feeds except those by Facebook.
    • We plan to introduce a connection-level setting for this in the future.

Update

Improvements

  • When reading events from iCalendar (ICS) feeds, ChronoLink now respects minimum update intervals suggested by the feed.

    • Previously, ChronoLink tried to fetch feeds every three minutes, which is the same interval it uses for Google Calendar, Outlook.com / Exchange Online and other sources.
    • With this change, we fix a problem with Facebook "upcoming events" feeds: after a few hours with the interval mentioned above, the Facebook servers would refuse requests for that feed for about 24 hours or more! Respecting the update interval they suggest in the feed (12 hours) solves this problem.
    • Note that you can always manually trigger a connection run regardless of when the next one is scheduled to occur.

    Finding the update interval

    Enter the address of the feed in a browser to view it, or download it and open it in a text editor.

    Search for a line starting with X-PUBLISHED-TTL. The value at the end of the line should look something like PT12H (12 hours), P2D (2 days) or P1W (1 week).

    If you can't find such a line, the update interval is unspecified and ChronoLink uses its default schedule.