Timeline View: Incorrect Time Alignment for Overlapping Tasks

Issue:
In the Timeline view, tasks that overlap are not positioned correctly against the time indicators on the left side of the screen.
As shown in the attached screenshot, the task details on the right display the correct scheduled times, but their visual placement does not align with the timeline on the left.
For example:
Laundry: Scheduled for 7:15 to 7:45 AM, but visually appears around 10:00 AM.
Bring Tesla to Tesla Collision: Scheduled for 8:00 to 9:00 AM, but visually appears around 11:00 AM.
Why this matters:
The Timeline view should provide a clear, chronological representation of my day. When tasks are visually misaligned with the time indicators, it becomes confusing to understand when activities are scheduled, especially when multiple tasks overlap.
Feature Request:
Please ensure that tasks are visually aligned with their actual scheduled times on the left timeline, even when tasks overlap.
Ideally, overlapping tasks should be displayed side by side or grouped in a way that preserves accurate time alignment.
Expected Behavior:
The timeline should maintain a consistent relationship between the time indicators on the left and the scheduled tasks on the right, making it easy to understand my schedule at a glance.

This request was merged into another request
Comments2
Linnea
Oct 21
Hi! This is happening because you have one very long event lasting the entire day (Analytics Innovation Review) which overlays with all following events.
Samir Sharma
Oct 21
Thanks, Linnea. I understand why the long event causes this behavior.
My concern is that the timeline becomes misleading when tasks are no longer visually aligned with their actual scheduled times. The purpose of a timeline is to provide an accurate representation of when events occur.
I recognize that screen space is limited, especially on mobile devices, but I believe maintaining accurate time alignment should be a core design principle.
Is this something the team is considering addressing, or is it expected behavior?