Skip to content

UI: Show duration chart tooltips in the selected timezone - #72024

Merged
bbovenzi merged 1 commit into
apache:mainfrom
rjgoyln:duration-chart-tooltip-timezone
Aug 31, 2026
Merged

bbovenzi merged 1 commit into
apache:mainfrom
rjgoyln:duration-chart-tooltip-timezone

Conversation

@rjgoyln

@rjgoyln rjgoyln commented Aug 24, 2026 •

Copy link
Copy Markdown
Contributor

Summary

The duration chart on the Dag and Task overview pages formatted its bar labels — which Chart.js reuses as the tooltip title — in the browser's local timezone, while the x-axis ticks and every other timestamp in the UI follow the timezone selected in the header. With the browser in Europe/Warsaw and Asia/Tokyo selected, a run at 2026-08-20T08:30:00Z is labeled 17:30:00 on the axis and 10:30:00 in the tooltip, so the tooltip no longer identifies the bar under the cursor. Labels now use the same formatDate call with the selected timezone that the axis already did.

Tests

The component had no tests; this adds one asserting the label text across three timezones.

related: #72018


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 5)

Generated-by: Claude Code (Opus 5) following the guidelines

The Last N Dag Runs / Task Instances chart formatted its bar labels in the
browser's local timezone while the x-axis ticks and the rest of the UI follow
the timezone picked in the header. Anyone whose machine sits in a different
timezone read a tooltip timestamp that did not identify the run they were
pointing at, which makes the chart misleading exactly when it is used to
compare runs.

Related: apache#72018
@bbovenzi bbovenzi added this to the Airflow 3.3.2 milestone Aug 31, 2026
@bbovenzi
bbovenzi merged commit f7a2f4e into apache:main Aug 31, 2026
172 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
✅ v3-3-test PR Link

bbovenzi pushed a commit that referenced this pull request Aug 31, 2026
…#72024) (#72339)

The Last N Dag Runs / Task Instances chart formatted its bar labels in the
browser's local timezone while the x-axis ticks and the rest of the UI follow
the timezone picked in the header. Anyone whose machine sits in a different
timezone read a tooltip timestamp that did not identify the run they were
pointing at, which makes the chart misleading exactly when it is used to
compare runs.
(cherry picked from commit f7a2f4e)


Related: #72018

Co-authored-by: rjgoyln <151457491+rjgoyln@users.noreply.github.com>
vatsrahul1001 pushed a commit that referenced this pull request Sep 7, 2026
…#72024) (#72339)

The Last N Dag Runs / Task Instances chart formatted its bar labels in the
browser's local timezone while the x-axis ticks and the rest of the UI follow
the timezone picked in the header. Anyone whose machine sits in a different
timezone read a tooltip timestamp that did not identify the run they were
pointing at, which makes the chart misleading exactly when it is used to
compare runs.
(cherry picked from commit f7a2f4e)


Related: #72018

Co-authored-by: rjgoyln <151457491+rjgoyln@users.noreply.github.com>
imrichardwu pushed a commit to imrichardwu/airflow that referenced this pull request Sep 11, 2026
The Last N Dag Runs / Task Instances chart formatted its bar labels in the
browser's local timezone while the x-axis ticks and the rest of the UI follow
the timezone picked in the header. Anyone whose machine sits in a different
timezone read a tooltip timestamp that did not identify the run they were
pointing at, which makes the chart misleading exactly when it is used to
compare runs.

Related: apache#72018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:UI Related to UI/UX. For Frontend Developers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants