Skip to content

[9.3] [Obs Explorations] Fix incorrect extraction of time range from wrong context (#248939)#249009

Merged
kibanamachine merged 2 commits intoelastic:9.3from
kibanamachine:backport/9.3/pr-248939
Jan 15, 2026
Merged

[9.3] [Obs Explorations] Fix incorrect extraction of time range from wrong context (#248939)#249009
kibanamachine merged 2 commits intoelastic:9.3from
kibanamachine:backport/9.3/pr-248939

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.3:

Questions ?

Please refer to the Backport tool documentation

…context (elastic#248939)

## Summary

Original issue - elastic#248795

As part of the original issue it was found that in 8.19 it provides a
completely broken experience but 9.1 onwards, we don't access the
undefined object inside the react component and straight away were
passing it to the Discover Locator which was getting `undefined` for
`dateRange` and thus was defaulting to `now to now-15m`

With this PR we fix passing the correct `dateRange`. Now when user open
`View in Context` and then clicks Open in Discover from the modal, it
does passes the actual timerange from the Logs Categories page to
Discover

## Release Note

Fixes broken links from View In Context Modal to Discover which was not
respecting the DateRange

(cherry picked from commit 6302c6b)
@kibanamachine kibanamachine merged commit 7cafc0b into elastic:9.3 Jan 15, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants