fix(dashboards): Respect fieldMeta overrides for timeseries widget types#107524
Merged
DominikB2014 merged 1 commit intomasterfrom Feb 3, 2026
Conversation
The extractSeriesMetadata function was setting fieldMeta values first, but then the API response metadata was overwriting them. This change ensures fieldMeta values take precedence by checking if the key already exists before setting from the API response.
github-actions
bot
added
the
Scope: Frontend
edwardgou-sentry
approved these changes
Feb 3, 2026
DominikB2014
deleted the
dominikbuszowiecki/browse-285-add-missing-units-to-backend-overview
branch
jaydgoss
pushed a commit
that referenced
this pull request
Feb 12, 2026
…pes (#107524) ## Summary - Fix `extractSeriesMetadata` to not overwrite `fieldMeta` values with API response metadata - `fieldMeta` values now take precedence as intended for custom type/unit overrides ## Problem The `fieldMeta` configuration (e.g., `{valueType: 'percentage'}`) was being set first but then immediately overwritten by the API response metadata. This caused custom type overrides to be ignored for timeseries widgets. ## Solution Check if the key already exists in the result (from `fieldMeta`) before setting from the API response. ## Test plan - Verify that widgets with `fieldMeta` configuration properly display percentage values instead of raw numbers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
extractSeriesMetadatato not overwritefieldMetavalues with API response metadatafieldMetavalues now take precedence as intended for custom type/unit overridesProblem
The
fieldMetaconfiguration (e.g.,{valueType: 'percentage'}) was being set first but then immediately overwritten by the API response metadata. This caused custom type overrides to be ignored for timeseries widgets.Solution
Check if the key already exists in the result (from
fieldMeta) before setting from the API response.Test plan
fieldMetaconfiguration properly display percentage values instead of raw numbers