Evolution for Calendar and Tasks on Ubuntu

Evolution’s Calendar and Tasks components remain among Ubuntu’s more capable organiser tools, even though GNOME Calendar and To Do now occupy the centre of the desktop. They cover appointments, recurring events, reminders, priorities and everyday to-dos without requiring a subscription to a commercial productivity platform.

The application suits people who want their schedules and task lists in one established suite. It also appeals to users of CalDAV services such as Nextcloud, although the interface feels noticeably older than the streamlined GNOME applications that shipped with recent Ubuntu releases.

Installing Evolution on Ubuntu

Evolution may not be installed by default, but Ubuntu’s own repositories provide everything needed. Open a terminal and run:

sudo apt update
sudo apt install evolution

Launch it from the Activities overview or type evolution into a terminal. The package includes the wider suite, with Mail, Calendar, Tasks, Contacts and address-book components sharing a common account system. You can ignore the email setup and use the organiser tools on their own.

The first-run wizard makes it easy to add a Google, Microsoft or CalDAV account, while skipping an account leaves you with a local calendar and task list. Evolution does not replace Ubuntu’s default calendar and task applications, nor does installing it change which application opens when you click the clock in the top panel.

Using the distribution package is preferable to downloading a random .deb file from an unfamiliar site. Updates then arrive through the normal Ubuntu mechanism. Anyone who prefers a containerised release should check its age and supported account features before choosing it over the repository version.

Calendar features that matter

The Calendar component provides day, week, month and list views, with a compact month navigator beside the main display. Multiple calendars can be colour-coded, overlaid and toggled independently, which works well for separating work, family, social commitments and public holidays. Creating an event takes only a few clicks, and events can be moved by dragging them around the grid.

An event editor handles start and finish times, all-day entries, locations, notes, attendees, categories, alarms and recurrence. Repeat rules can cover weekly or monthly appointments, while individual occurrences can be altered without disturbing the entire series. Availability information and invitation replies are supported, making it useful for organising meetings with colleagues as well as personal appointments.

The calendar’s information density is one of its strengths on a large monitor. A busy month remains readable, and list or week views are effective when several appointments overlap. On a small screen, however, month cells become cramped and some event labels are truncated. The agenda-oriented views are generally more comfortable on a laptop or tablet, particularly when Evolution is running in a narrow window.

Accounts, calendars and time zones

Account setup handles most mainstream calendar services. Google and Microsoft accounts can be connected through Evolution’s account assistant, while Nextcloud and other CalDAV servers can be configured manually with a server address, username and application password. Provider support varies, so authentication policies and advanced scheduling features should be tested before moving an entire diary across.

A useful distinction is that connecting Google Calendar does not connect Google Tasks or Reminders. Evolution’s separate task system does not synchronise with Google Tasks, Microsoft To Do, Trello or a similar project board. Calendar events and to-dos may look like a unified workflow inside Evolution, but their underlying destinations are different.

For Australian users, time-zone handling deserves attention. Sydney and Melbourne usually observe UTC+10, Brisbane uses UTC+10, Perth uses UTC+8 and Darwin sits at UTC+9:30. Daylight saving shifts the clock in much of southern Australia, so a recurring meeting can move relative to its usual local time. Floating all-day events are useful for birthdays and anniversaries, while a precisely timed event should carry an explicit time zone when people join from different states.

There is no automatic assumption that an Australian public holiday belongs in every calendar. Australia Day on 26 January, ANZAC Day on 25 April and Boxing Day on 26 December can be added as all-day entries, with state-specific holidays sourced from the relevant government calendar. Subscription calendars are worth checking carefully because some include substitute days observed on Monday.

Tasks for daily errands and reminders

Tasks is a straightforward to-do manager rather than a visual project planner. A memo can include a summary, due date, priority, percentage complete, categories, notes and a private flag. These fields cover shopping lists, household errands, study assignments and short work checklists without the ceremony of setting up a project around each one.

The interface presents pending items, completed items and saved searches. Categories allow a little organisation without becoming complicated, and sorting by due date makes overdue work obvious. Because Evolution uses a shared data layer, the Tasks component can exist independently of an email account or online calendar.

Its limitations are equally clear. It does not provide the richer hierarchy, automation and cross-project views expected from a dedicated work-management application. Calendar recurrence rules should not be confused with repeating tasks; recurring chores are often easier to represent as calendar events with an alarm, then duplicate the relevant task manually when required. Built-in task reminders also need care, especially when Evolution is not open.

Task portability is another consideration. Calendar events are straightforward to export as .ics files, but moving Evolution’s task data to another platform generally requires more manual work. People considering a migration should treat the task list as something to test carefully rather than assuming that a successful calendar connection has transferred every item.

An interface with visible age

Evolution looks more functional than decorative. Menus, toolbars and small icons provide access to many settings, but the layout does not feel as calm or immediate as GNOME Calendar and To Do. Its older GNOME styling may still feel familiar to longtime Ubuntu users, while newcomers may need a little time to identify which controls affect the selected event.

Keyboard access is serviceable, although some icons do not explain themselves well and a few dialogs feel busier than modern GNOME applications. The system font, colour scheme and GTK theme are respected broadly, so Evolution does not look completely out of place on Ubuntu. Even so, visual consistency is not the same as interface consistency: the suite sometimes presents the same concept in different words across Calendar, Mail and Contacts.

Performance is usually unremarkable with a personal diary containing several years of appointments. Large calendars and numerous accounts can make searching or switching views feel slower than in a lightweight standalone application. The top-panel clock also opens GNOME Calendar rather than Evolution, which may catch users moving between the two without expecting their entries to appear in the same place.

Ubuntu’s wider application library is a genuine advantage, though. For a change of pace, the Krita digital painting guide shows how another creative GNOME application fits into the desktop, with Evolution remaining available to schedule studio sessions and client meetings.

A practical starting point

Evolution earns its place for people who want a mature calendar, a modest task manager and account support in one package. It is particularly sensible for Nextcloud users, households with shared calendars and anyone who prefers local files over relying entirely on a cloud productivity service. GNOME Calendar paired with To Do will usually feel faster and cleaner for a Google-centred workflow.

Before migrating, test the connections that matter. Confirm that events appear on a second device, invitations reach attendees and alarms arrive when expected. Export important calendars, back up the local Evolution data while the applications are closed, and keep a separate copy of anything not stored on a server.

The concrete next step is to open Evolution, create one test event for tomorrow at 9:00 am and one task due tomorrow, then restart the applications and verify that both entries remain intact.