[9.3] Adhere to user selected time range for CSV exports (#255005)#266429
Merged
eokoneyo merged 1 commit intoelastic:9.3from Apr 30, 2026
Merged
[9.3] Adhere to user selected time range for CSV exports (#255005)#266429eokoneyo merged 1 commit intoelastic:9.3from
eokoneyo merged 1 commit intoelastic:9.3from
Conversation
## Summary Closes elastic#216605 This PR adds implementation such that when generating a CSV export within Kibana from the discover app the absolute time range for the current session is used, whilst for retain the currently behaviour for the generated POST URL, this ensures that the export the user gets correlates one to one with the exact content the user is currently viewing. ## Implementation A new property `absoluteTimeRange` is now being passed to the sharing data for the discover app, this property is then used whilst generating a CSV export within Kibana, POST URL retains it's normal behavior of having the value the user selected in the UI, see (elastic#255005 (comment)) for the rationale behind this decision. ### Visual There is no visual change to the user. <!-- ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit dd1ca76) # Conflicts: # packages/kbn-optimizer/limits.yml # src/platform/packages/private/kbn-reporting/public/share/integrations/csv/csv_export_config.tsx # src/platform/plugins/shared/discover/moon.yml # src/platform/plugins/shared/discover/public/application/main/components/top_nav/app_menu_actions/get_share.tsx # src/platform/plugins/shared/discover/tsconfig.json # src/platform/plugins/shared/share/public/components/export_integrations/export_integrations.tsx # src/platform/plugins/shared/share/public/components/export_integrations/index.ts # src/platform/plugins/shared/share/public/services/share_menu_manager.tsx
eokoneyo
force-pushed
the
backport/9.3/pr-255005
branch
from
beac9f2 to
33a5222
Compare
Contributor
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Async chunks
Page load bundle
History
|
kowalczyk-krzysztof
approved these changes
Apr 30, 2026
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
3 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.
Backport
This will backport the following commits from
mainto9.3:Questions ?
Please refer to the Backport tool documentation