mirror of
https://github.com/elastic/kibana.git
synced 2025-04-22 08:49:27 -04:00
4215a637da
## Summary
Scripted fields in data views have been deprecated since 7.13, and
superseded by runtime fields.
The ability to create new scripted fields has been removed from the Data
Views management page in 9.0. Existing scripted fields can still be
edited or deleted, and the creation UI can be accessed by navigating
directly to
`/app/management/kibana/dataViews/dataView/{dataViewId}/create-field`,
but it is recommended to migrate to runtime fields or ES|QL instead to
prepare for removal.
Additionally, the scripted fields entry in the Upgrade Assistant has
been updated to reflect these changes, improve migration instructions,
and surface the full list of data views across all spaces that contain
scripted fields as well as their associated spaces. New documentation
has been added to the "Manage data views" page with examples and
instructions to help users migrate off scripted fields to runtime fields
or ES|QL, which is also linked to from the Upgrade Assistant entry.
Data Views management page:
Upgrade Assistant:
<img
src="https://github.com/user-attachments/assets/4ff27866-4fe8-4357-82e8-cd4c503ab50b"
width="500" />
Resolves #182067.
### Checklist
- [x] 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/packages/kbn-i18n/README.md)
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [x] [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)
- [x] 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
- [x] 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)
---------
Co-authored-by: Matt Kime <matt@mattki.me>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
|
||
|---|---|---|
| .. | ||
| analytics | ||
| application | ||
| apps | ||
| base | ||
| capabilities | ||
| chrome | ||
| config/core-config-server-internal | ||
| custom-branding | ||
| deprecations | ||
| doc-links | ||
| elasticsearch | ||
| environment | ||
| execution-context | ||
| fatal-errors | ||
| feature-flags | ||
| http | ||
| i18n | ||
| injected-metadata | ||
| integrations | ||
| lifecycle | ||
| logging | ||
| metrics | ||
| mount-utils | ||
| node | ||
| notifications | ||
| overlays | ||
| plugins | ||
| preboot | ||
| rendering | ||
| root | ||
| saved-objects | ||
| security | ||
| status | ||
| test-helpers | ||
| theme | ||
| ui-settings | ||
| usage-data | ||
| user-profile | ||
| user-settings | ||