This guide explains how ActivityTimeline handles two types of non-Jira events in Timesheets:
-
External calendar events imported from Google Calendar, Outlook, or another connected calendar.
-
Internal booking-type events created directly within ActivityTimeline.
You can configure whether these events should be treated as worklogs and included in Timesheets, or whether they should remain visible only as planning events.
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.
To configure this, go to:
My Account → Calendar Integration
Log Time from External Calendar Events
You can choose how imported calendar events (e.g. meetings from Outlook or Google Calendar) should appear in ActivityTimeline:
-
Treat all as Worklogs (default)
-
Treat none as Worklogs
To configure this, go to:
Configuration → Timesheets Config → External Calendar Worklog Behaviour
Options Overview
|
Option Name |
What It Does |
Best For |
|---|---|---|
|
Treat all as Worklogs (default) |
All imported external calendar events are automatically counted as logged time. |
Teams that log all meetings or external events by default |
|
Treat none as Worklogs |
Imported calendar events are shown in ActivityTimeline, but they are not automatically counted as worklogs. Users can manually log time from the event by linking it to Jira issue |
Teams that want user control over what's logged |
Examples
-
Treat all as Worklogs
-
If a user has a calendar event called Team Sync Meeting, ActivityTimeline will import the event and include its duration as logged time without requiring any additional action from the user.
-
Treat none as Worklogs
When Treat none as Worklogs is selected, imported external calendar events appear on the user’s timeline, but they are not automatically counted as worklogs.
User has a 1-hour event called Client Sync Meeting in Google Calendar. The event appears on his ActivityTimeline timeline. User clicks Log Time, selects the relevant Jira issue, for example MOB-321, and saves the worklog.
Handling Internal Booking-Type Events
Internal booking-type events are assignments created directly in ActivityTimeline that are not linked to Jira issues. They are often used to reserve user capacity for internal work, tentative assignments, training, meetings, or work that does not need to be represented as a Jira issue.
Administrators can define whether Booking events should be included in Timesheets as worklogs.
To configure this, go to:
Configuration → Timesheets Config → Treat Booking Items as Worklogs
Options Overview
|
Option Name |
What It Does |
Best For |
|---|---|---|
|
Checked |
Booking events are included in Timesheets and treated as worklogs. |
Teams that use Bookings to represent planned or internal work that should count as logged time. |
|
Unchecked |
Booking events are not included in Timesheets or worklog reports. |
Teams that want Timesheets to include only Jira-linked worklogs. |
Examples
Watch the video below to see an example of how ActivityTimeline behaves when Treat Booking Items as Worklogs is enabled.
ActivityTimeline also allows administrators to configure custom event types based on the Booking system event type.
For each custom Booking-based event type, you can define whether it should be treated as a worklog or not.
This is useful when some Booking-type events should count as work, while others should remain only planning items.
To configure this behavior, edit the relevant event type under:
Configuration → Events → Manage → Update Category -> ‘Not a Worklog’
Summary
|
Type |
Event Source |
Options |
Main Use Case |
|---|---|---|---|
|
External Calendar Events |
Google/Outlook |
Manual logging or Auto-logging |
Meetings, personal calendar, external calls |
|
Booking-Type Events |
ActivityTimeline |
Show as worklogs or Hide from timesheet |
Internal activities, training, non-Jira tasks |