Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.14] es query rule - get time field from data view instead of rule (#…
…182883) (#183001) # Backport This will backport the following commits from `main` to `8.14`: - [es query rule - get time field from data view instead of rule (#182883)](#182883) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-05-08T22:00:24Z","message":"es query rule - get time field from data view instead of rule (#182883)\n\n## Summary\r\n\r\nPreviously it was possible to create a rule with a data view and change\r\nthe data view but the previous time field would still be referenced. Now\r\nthe time field is always pulled from the current data view.\r\n\r\n\r\nCloses https://github.com/elastic/kibana/issues/182879\r\n\r\n#### Release note\r\n\r\nFixed issue where an ES query rule could be created with a data view,\r\nthen the data view is changed but there's still a reference to the\r\nprevious data view's timestamp field. Now the timestamp field is always\r\ntaken from the currently configured data view.\r\n\r\n---------\r\n\r\nCo-authored-by: Davis McPhee <[email protected]>","sha":"bc103c7016245901a04fc4921c1b213a4fbe2695","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:DataDiscovery","backport:prev-minor","v8.15.0"],"title":"es query rule - get time field from data view instead of rule","number":182883,"url":"https://github.com/elastic/kibana/pull/182883","mergeCommit":{"message":"es query rule - get time field from data view instead of rule (#182883)\n\n## Summary\r\n\r\nPreviously it was possible to create a rule with a data view and change\r\nthe data view but the previous time field would still be referenced. Now\r\nthe time field is always pulled from the current data view.\r\n\r\n\r\nCloses https://github.com/elastic/kibana/issues/182879\r\n\r\n#### Release note\r\n\r\nFixed issue where an ES query rule could be created with a data view,\r\nthen the data view is changed but there's still a reference to the\r\nprevious data view's timestamp field. Now the timestamp field is always\r\ntaken from the currently configured data view.\r\n\r\n---------\r\n\r\nCo-authored-by: Davis McPhee <[email protected]>","sha":"bc103c7016245901a04fc4921c1b213a4fbe2695"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/182883","number":182883,"mergeCommit":{"message":"es query rule - get time field from data view instead of rule (#182883)\n\n## Summary\r\n\r\nPreviously it was possible to create a rule with a data view and change\r\nthe data view but the previous time field would still be referenced. Now\r\nthe time field is always pulled from the current data view.\r\n\r\n\r\nCloses https://github.com/elastic/kibana/issues/182879\r\n\r\n#### Release note\r\n\r\nFixed issue where an ES query rule could be created with a data view,\r\nthen the data view is changed but there's still a reference to the\r\nprevious data view's timestamp field. Now the timestamp field is always\r\ntaken from the currently configured data view.\r\n\r\n---------\r\n\r\nCo-authored-by: Davis McPhee <[email protected]>","sha":"bc103c7016245901a04fc4921c1b213a4fbe2695"}}]}] BACKPORT--> Co-authored-by: Matthew Kime <[email protected]>
- Loading branch information