mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
9a3dd16bd0
# Backport This will backport the following commits from `main` to `8.9`: - [[data view editor] Fix data view timestamp validation (#150398)](https://github.com/elastic/kibana/pull/150398) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2023-06-30T12:29:44Z","message":"[data view editor] Fix data view timestamp validation (#150398)\n\n## Summary\r\n\r\nPreviously - If you changed a data view's index pattern AND the new\r\npattern didn't contain the timestamp field, you'd see a blank timestamp\r\nfield and it would let you save. The data view would have been saved\r\nwith the previous timestamp field which doesn't exist.\r\n\r\nNow - The timestamp validator checks to make sure the selected timestamp\r\nfield is in the list of available options. This is helpful because it\r\nkeeps the previous timestamp value in case you do select an index\r\npattern that contains it.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/150219","sha":"646539c45b454b48c9fa985b7ac5cb69a63c70f8","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Data Views","Feature:Kibana Management","Team:DataDiscovery","backport:prev-minor","v8.10.0"],"number":150398,"url":"https://github.com/elastic/kibana/pull/150398","mergeCommit":{"message":"[data view editor] Fix data view timestamp validation (#150398)\n\n## Summary\r\n\r\nPreviously - If you changed a data view's index pattern AND the new\r\npattern didn't contain the timestamp field, you'd see a blank timestamp\r\nfield and it would let you save. The data view would have been saved\r\nwith the previous timestamp field which doesn't exist.\r\n\r\nNow - The timestamp validator checks to make sure the selected timestamp\r\nfield is in the list of available options. This is helpful because it\r\nkeeps the previous timestamp value in case you do select an index\r\npattern that contains it.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/150219","sha":"646539c45b454b48c9fa985b7ac5cb69a63c70f8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/150398","number":150398,"mergeCommit":{"message":"[data view editor] Fix data view timestamp validation (#150398)\n\n## Summary\r\n\r\nPreviously - If you changed a data view's index pattern AND the new\r\npattern didn't contain the timestamp field, you'd see a blank timestamp\r\nfield and it would let you save. The data view would have been saved\r\nwith the previous timestamp field which doesn't exist.\r\n\r\nNow - The timestamp validator checks to make sure the selected timestamp\r\nfield is in the list of available options. This is helpful because it\r\nkeeps the previous timestamp value in case you do select an index\r\npattern that contains it.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/150219","sha":"646539c45b454b48c9fa985b7ac5cb69a63c70f8"}}]}] BACKPORT--> Co-authored-by: Matthew Kime <matt@mattki.me> |
||
|---|---|---|
| .. | ||
| accessibility | ||
| analytics | ||
| api_integration | ||
| common | ||
| examples | ||
| functional | ||
| harden | ||
| health_gateway | ||
| interactive_setup_api_integration | ||
| interactive_setup_functional | ||
| interpreter_functional | ||
| node_roles_functional | ||
| package | ||
| plugin_functional | ||
| scripts | ||
| server_integration | ||
| ui_capabilities/newsfeed_err | ||
| tsconfig.json | ||