Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Annotations were being incorrectly placed and labeled on timeseries charts because they didn't account for the dashboard timezone. See #8633 for discussion of a similar issue.
The problem was here:
This converts a UTC ISO timestamp into a JS Date using the local timezone, so all subsequent label generation and date transformations happened in local time rather than the selected dashboard timezone.
The fix passes
dashboardTimezonethrough from the explore state and usesDateTime.fromISO()with that timezone, then converts to a JS Date usingsetZone(localTimezone, { keepLocalTime: true })so the annotation renders at the correct visual position.Example: Viewing a dashboard set to UTC with a local system in New Delhi, an annotation timestamped
2025-06-22T08:00:00Zrendered like this on 0.78:After the fix:
Comprehensive tests will be added in a follow-up PR.
Checklist: