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.
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.
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.
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.
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.
Connections with Google Calendar sinks that contain many events now run much faster and therefore more frequently.
Previously, connections with sink calendars that have hundreds or thousands of non-ChronoLink events could run for several minutes even when there was nothing to do. Some connections even took 15 or 20 minutes!
Now, thanks to our new approach, most such runs complete in less than 20 seconds. Also, the total number of runs per hour increased by 60%.
Users can now opt in to synchronizing PENDING or DECLINED meeting invitations by using the new include transformer.
Previously, ChronoLink always skipped such invitations.
Added the exclude transformer to allow excluding an event from the synchronization run.
Using the exclude transformer on an event is effectively equivalent to filtering out that event with a suitable condition.
The organizer condition now also allows checking only the domain of the meeting organizer.
Previously, this functionality was offered by the organizerdomain condition, which has now been removed. Existing connections using organizerdomain have been migrated automatically.
ChronoLink now supports accessing calendars via the iCalendar (ICS) standard.
This feature can be used to connect many different systems which ChronoLink does not support natively. Therefore, it depends on the respective system which kind of event data is included.
In addition, connecting via an iCalendar address can help in case your organization's administrators have restricted access by apps like ChronoLink.
Usage: create a new connection, open the "Source" selection list, scroll down to locate the "Other" section and choose the option "iCalendar". Then, enter the URL given by the other system in the "Source Calendar Address" field.
The ChronoLink configuration page now lists all linked accounts in one table, regardless of whether they are set up for login, calendar access, or both.
Previously, linked accounts were listed in two tables called "Login" and "Access". As user feedback showed us that this strict separation made initial setup more difficult, we removed it.
If any connection references a linked account, ChronoLink no longer allows deleting the calendar access from that account.
This change prevents users from accidentally deleting their connections together with the calendar access.
ChronoLink now synchronizes event visibility for Google and Microsoft calendars:
If the Source and Sink are in the same system, the created event will have the same visibility as the source.
In case of different systems, PRIVATE visibility will be kept. Other visibility values will be translated to their closest equivalent. For details, see the corresponding table in our docs.
To increase performance and punctuality of scheduled runs, multiple connections from the same ChronoLink account are now allowed to run at the same time.
Previously, we prevented this to make sure that users with many connections did not slow down other users.
Having recently rewritten our connection queue, we can now achieve the same goal in a better way: we always favor any due connection from users who have no currently running connection. Then, any leftover capacity is used to run additional connections for other users.
We made minor changes to the configuration page in order to make it less confusing:
The connection label field is now called "Name" and has a placeholder text to make its purpose more obvious. Also, it was moved to the top of the form, where one would expect a name field to be.
We added borders to the login, access and connection tables. This ensures they are still recognizable as tables even when they are empty. We now also display "You don't have access to any calendars yet" and "You don't have any connections yet" messages in that situation.
Added the limit condition to restrict the number of synchronized events. For example, this allows synchronizing only the first event for each day or week.