The Timeline Panel tab in ActivityTimeline Configuration allows Jira administrators to customize how timelines, events, issues, and calendar-related elements are displayed in ActivityTimeline.
These settings are divided into two main sections:
-
Timeline View
-
Events
Timeline View
The Timeline View section controls the visual appearance of the Planner timeline and calendar behavior.
Default Colors
You can define default colors for the main elements displayed on the timeline:
-
Default color for issues — sets the default color for Jira issue bars on the timeline.
-
Default color for work events — sets the default color for custom work events, such as Notes, Bookings, Placeholders, and similar event types.
-
Default color for non-working events — sets the default color for events that reduce user capacity, such as Vacations, Holidays, Days Off, and other non-working events.
These colors help users visually distinguish between Jira tasks, planned work events, and time-off or non-working periods.
Automatically Color Issues Based on Epics
When Automatically color issues based on Epics is enabled, ActivityTimeline applies the same background color to all tasks linked to the same Epic.
This makes it easier to distinguish work related to different Epics directly on the timeline.
For example, all tasks linked to Epic A will have one color, while tasks linked to Epic B will have another color.
By default, this setting is disabled.
Calendar Settings
This section also includes several settings that define how dates and calendar periods are displayed.
You can configure:
-
First Day of the Week — defines which day is shown as the first day of the calendar week.
-
First Week of Year — defines how week numbering is calculated.
-
Weekend Displaying Mode — allows you to show weekends as thin columns or full-sized columns.
-
Time Format — allows you to use either a 12-hour or 24-hour time format.
-
Number of users displayed on timeline — defines how many users are shown per timeline page
Planned Start/End Dates Format
The Planned Start/End Dates format setting defines whether ActivityTimeline should treat mapped planned date fields as:
-
Date Only
-
Date/Time
Use Date Only if your planned start and planned end fields in Jira are Date Picker fields.
Use Date/Time if your planned start and planned end fields in Jira are Date/Time Picker fields.
Date/Time mode allows tasks to be scheduled within a specific time range during the day, rather than only across full days.
If you want to use Date/Time mode, make sure that the mapped planned start and planned end fields in Jira are also Date/Time Picker custom fields. These fields are configured in Configuration → Jira Integration.
That said, we generally do not recommend using hour planning unless it’s strictly required. When working with hours, time zone differences between users, Jira settings, and browsers can lead to unexpected shifts in start or end times, especially in distributed teams.
Show Issues on Timelines Based on a Single Date
When this option is enabled, ActivityTimeline can display issues on the timeline even if only one planned date is filled in.
For example, an issue can be displayed if it has only a start date or only an end date.
When this option is disabled, ActivityTimeline displays issues on timelines only when both planned start and planned end dates are available.
Events
The Events section controls how Jira issues, dependencies, custom events, resolved tickets, overdue items, and milestone-related items behave on the timeline.
Track Blocked Issues
The Track blocked issues setting defines whether ActivityTimeline should track dependencies between Jira issues.
When enabled, ActivityTimeline tracks Jira issue links such as:
-
blocks
-
is blocked by
This helps users identify dependencies directly in ActivityTimeline.
By default, this setting is disabled. Learn more: Issue Dependency
Confirmation on Event Removal
The Confirmation on Event removal setting defines whether ActivityTimeline should show a confirmation dialog when a user removes a custom event.
When enabled, users will be asked to confirm the action before the event is deleted.
When disabled, custom events can be removed without an additional confirmation.
By default, this setting is enabled.
Create Jira Issues Through ActivityTimeline
The Create Jira issues through ActivityTimeline setting controls how new Jira issues are created from ActivityTimeline.
When enabled, users can create new Jira issues directly from ActivityTimeline.
When disabled, ActivityTimeline opens the native Jira issue creation page in a popup.
By default, this setting is enabled.
Displaying of Resolved Tickets
The Displaying of Resolved Tickets setting controls whether resolved Jira issues should be shown on timelines and whether their remaining estimates should be counted in workload calculations.
Available options include:
-
Show resolved tickets and count their remaining estimate for workload
-
Show resolved tickets but do not count their remaining estimate for workload
-
Hide resolved tickets and do not count their remaining estimate for workload
This setting is useful when resolved issues still have remaining estimates in Jira, but you do not want them to affect users’ workload in ActivityTimeline.
Default value: Show on timelines with remaining estimates.
Issue Statuses to Mark as Resolved
The Issue statuses to mark as Resolved setting helps ActivityTimeline understand which Jira statuses should be treated as resolved.
This is useful because Jira instances may use different workflow statuses to indicate that work is complete.
Default values: Done, Closed.
Show Overdue Issues Counter per User
The Show Overdue Issues Counter per User setting displays a small counter next to each user on the Planner timeline.
This counter shows the number of unresolved issues that have a missed due date or were not resolved on time.
When enabled, the overdue counter appears in red near the user’s workload indicator. Users can click the counter to view the overdue or expired tickets.
By default, this setting is disabled.
Display Issues on the Milestones Panel Based on Due Date
The Display Issues on the Milestones Panel based on Due date setting allows Jira issues to appear on the Milestones Panel based on their Due Date field.
When enabled, the Milestones Panel can show not only releases but also Jira tasks with due dates.
This helps teams track important delivery dates and issue-level deadlines in the same panel.
By default, this setting is disabled.
Deadline Warning Period
The Deadline Warning Period setting defines how many days before the issue due date ActivityTimeline should start visually emphasizing the task.
For example, if the value is set to 7, tasks with a due date within the next 7 days the text of issue will be in bold.
If the due date is closer than the configured warning period, the task will appear emphasized on the timeline, for example in bold black text by default.
Default value: 7 days.