You can configure whether these events should appear in timesheets as loggable work or be ignored entirely.
1. Handling External Calendar Events
When you connect an external calendar, ActivityTimeline can import scheduled events. You have full control over how these events are treated in your team's timesheets.
Configuration Location: Go to My Account → Calendar integration:
Log Time from External Calendar Events
Choose how imported calendar events (e.g. meetings from Outlook or Google Calendar) should appear in ActivityTimeline:
Let users log time manually from these events
Log them automatically as worklogs
Or don’t show them in the timesheet at all
Options Overview
Option Name
What It Does
Best For
Manual Time Logging (Default)
Calendar events appear in ActivityTimeline, and users can log time by choosing a Jira issue
Teams that want user control over what's logged
Automatic Logging
All imported events are instantly saved as Jira worklogs
Teams that log all meetings or external events by default
Do Not Show or Log Events
External events are not displayed in the timesheet and can’t be logged
Teams that don’t want to use external calendars for time tracking
Example:
SCREENSHOT / VIDEO (Loom)
Manual Logging: Bob has a 1-hour event titled “Design Review Meeting” in her Google Calendar. It appears in her timeline in ActivityTimeline. He clicks “Log Time”, selects the Jira ticket “MOB-321,” and saves it.
SCREENSHOT / LOOM Video (Track, all events logged as worklogs)
Automatic Logging: All external events like “Team Sync” or “Client Call” are logged to Jira automatically, without user action.
2. Handling Internal Booking-Type Events
Internal booking-type events are assignments created directly in ActivityTimeline that are not linked to Jira issues. You can choose whether to treat these bookings as actual worklogs.
Setting Location: Go to Configuration → Timesheet Configuration → Treat Bookings as worklogs
You can decide whether bookings created in ActivityTimeline (not linked to Jira issues) should appear in timesheets as logged work. Useful for tracking estimated time or pre-assigned work without needing a Jira issue.
Option Name
What It Does
Best For
Checked
Bookings appear in timesheets as if they were logged work
When you want to track internal work or placeholders
Unchecked
Bookings do not appear in timesheets or worklog reports
When only Jira-linked work should be reported
Note, you can configure whether to treat custom events based on the Booking type as worklogs or not. You can simply configure these events so that they are not treated as worklogs:
