Adding time field to get data views response schema#235975
Merged
jgowdyelastic merged 3 commits intoelastic:mainfrom Sep 23, 2025
Merged
Conversation
jgowdyelastic
added
bug
jgowdyelastic
changed the title
kertal
approved these changes
Sep 23, 2025
Contributor
|
Starting backport for target branches: 9.1 |
Contributor
💚 Build Succeeded
Metrics [docs]
History
|
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 23, 2025
`timeFieldName` was missing from the response schema and so the public api call fails. Note, the data views page in stack management does not use this endpoint and considering this bug hasn't been noticed until now, I believe only external tools call this public endpoint. **Before** <img width="1365" height="216" alt="image" src="https://github.com/user-attachments/assets/a12e0ca6-aa55-4e27-be0c-a62d303f10b2" /> **After** <img width="1367" height="359" alt="image" src="https://github.com/user-attachments/assets/002fc551-37f5-494e-a01f-b9ec0abc3d55" /> ### 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: Matthias Polman <matthias.wilhelm@elastic.co> (cherry picked from commit 15b74e3)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Sep 23, 2025
…236060) # Backport This will backport the following commits from `main` to `9.1`: - [Adding time field to get data views response schema (#235975)](#235975) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2025-09-23T09:04:42Z","message":"Adding time field to get data views response schema (#235975)\n\n`timeFieldName` was missing from the response schema and so the public\napi call fails.\nNote, the data views page in stack management does not use this endpoint\nand considering this bug hasn't been noticed until now, I believe only\nexternal tools call this public endpoint.\n\n**Before**\n<img width=\"1365\" height=\"216\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a12e0ca6-aa55-4e27-be0c-a62d303f10b2\"\n/>\n\n**After**\n<img width=\"1367\" height=\"359\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/002fc551-37f5-494e-a01f-b9ec0abc3d55\"\n/>\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Matthias Polman <matthias.wilhelm@elastic.co>","sha":"15b74e33902101197ce25ab9e2c10dfa5f2f7ea9","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Feature:Data Views","backport:version","v9.2.0","v9.1.5"],"title":"Adding time field to get data views response schema","number":235975,"url":"https://github.com/elastic/kibana/pull/235975","mergeCommit":{"message":"Adding time field to get data views response schema (#235975)\n\n`timeFieldName` was missing from the response schema and so the public\napi call fails.\nNote, the data views page in stack management does not use this endpoint\nand considering this bug hasn't been noticed until now, I believe only\nexternal tools call this public endpoint.\n\n**Before**\n<img width=\"1365\" height=\"216\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a12e0ca6-aa55-4e27-be0c-a62d303f10b2\"\n/>\n\n**After**\n<img width=\"1367\" height=\"359\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/002fc551-37f5-494e-a01f-b9ec0abc3d55\"\n/>\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Matthias Polman <matthias.wilhelm@elastic.co>","sha":"15b74e33902101197ce25ab9e2c10dfa5f2f7ea9"}},"sourceBranch":"main","suggestedTargetBranches":["9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/235975","number":235975,"mergeCommit":{"message":"Adding time field to get data views response schema (#235975)\n\n`timeFieldName` was missing from the response schema and so the public\napi call fails.\nNote, the data views page in stack management does not use this endpoint\nand considering this bug hasn't been noticed until now, I believe only\nexternal tools call this public endpoint.\n\n**Before**\n<img width=\"1365\" height=\"216\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a12e0ca6-aa55-4e27-be0c-a62d303f10b2\"\n/>\n\n**After**\n<img width=\"1367\" height=\"359\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/002fc551-37f5-494e-a01f-b9ec0abc3d55\"\n/>\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Matthias Polman <matthias.wilhelm@elastic.co>","sha":"15b74e33902101197ce25ab9e2c10dfa5f2f7ea9"}},{"branch":"9.1","label":"v9.1.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> Co-authored-by: Matthias Polman <matthias.wilhelm@elastic.co>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Sep 24, 2025
`timeFieldName` was missing from the response schema and so the public api call fails. Note, the data views page in stack management does not use this endpoint and considering this bug hasn't been noticed until now, I believe only external tools call this public endpoint. **Before** <img width="1365" height="216" alt="image" src="https://github.com/user-attachments/assets/a12e0ca6-aa55-4e27-be0c-a62d303f10b2" /> **After** <img width="1367" height="359" alt="image" src="https://github.com/user-attachments/assets/002fc551-37f5-494e-a01f-b9ec0abc3d55" /> ### 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: Matthias Polman <matthias.wilhelm@elastic.co>
jgowdyelastic
added a commit
that referenced
this pull request
Sep 24, 2025
Related to #235975 `managed` was also missing from the response schema and so the public api call fails. Checking against the type [DataViewListItem](https://github.com/elastic/kibana/blob/2e9bcbb3126389520706ef100813efd47adaee4a/src/platform/plugins/shared/data_views/common/data_views/data_views.ts#L64), this list should now definitely be correct.
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 24, 2025
Related to elastic#235975 `managed` was also missing from the response schema and so the public api call fails. Checking against the type [DataViewListItem](https://github.com/elastic/kibana/blob/2e9bcbb3126389520706ef100813efd47adaee4a/src/platform/plugins/shared/data_views/common/data_views/data_views.ts#L64), this list should now definitely be correct. (cherry picked from commit a88eff1)
rbrtj
pushed a commit
to rbrtj/kibana
that referenced
this pull request
Sep 25, 2025
Related to elastic#235975 `managed` was also missing from the response schema and so the public api call fails. Checking against the type [DataViewListItem](https://github.com/elastic/kibana/blob/2e9bcbb3126389520706ef100813efd47adaee4a/src/platform/plugins/shared/data_views/common/data_views/data_views.ts#L64), this list should now definitely be correct.
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this pull request
Sep 25, 2025
Related to elastic#235975 `managed` was also missing from the response schema and so the public api call fails. Checking against the type [DataViewListItem](https://github.com/elastic/kibana/blob/2e9bcbb3126389520706ef100813efd47adaee4a/src/platform/plugins/shared/data_views/common/data_views/data_views.ts#L64), this list should now definitely be correct.
niros1
pushed a commit
that referenced
this pull request
Sep 30, 2025
`timeFieldName` was missing from the response schema and so the public api call fails. Note, the data views page in stack management does not use this endpoint and considering this bug hasn't been noticed until now, I believe only external tools call this public endpoint. **Before** <img width="1365" height="216" alt="image" src="https://github.com/user-attachments/assets/a12e0ca6-aa55-4e27-be0c-a62d303f10b2" /> **After** <img width="1367" height="359" alt="image" src="https://github.com/user-attachments/assets/002fc551-37f5-494e-a01f-b9ec0abc3d55" /> ### 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: Matthias Polman <matthias.wilhelm@elastic.co>
niros1
pushed a commit
that referenced
this pull request
Sep 30, 2025
Related to #235975 `managed` was also missing from the response schema and so the public api call fails. Checking against the type [DataViewListItem](https://github.com/elastic/kibana/blob/2e9bcbb3126389520706ef100813efd47adaee4a/src/platform/plugins/shared/data_views/common/data_views/data_views.ts#L64), this list should now definitely be correct.
rylnd
pushed a commit
to rylnd/kibana
that referenced
this pull request
Oct 17, 2025
`timeFieldName` was missing from the response schema and so the public api call fails. Note, the data views page in stack management does not use this endpoint and considering this bug hasn't been noticed until now, I believe only external tools call this public endpoint. **Before** <img width="1365" height="216" alt="image" src="https://github.com/user-attachments/assets/a12e0ca6-aa55-4e27-be0c-a62d303f10b2" /> **After** <img width="1367" height="359" alt="image" src="https://github.com/user-attachments/assets/002fc551-37f5-494e-a01f-b9ec0abc3d55" /> ### 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: Matthias Polman <matthias.wilhelm@elastic.co>
rylnd
pushed a commit
to rylnd/kibana
that referenced
this pull request
Oct 17, 2025
Related to elastic#235975 `managed` was also missing from the response schema and so the public api call fails. Checking against the type [DataViewListItem](https://github.com/elastic/kibana/blob/2e9bcbb3126389520706ef100813efd47adaee4a/src/platform/plugins/shared/data_views/common/data_views/data_views.ts#L64), this list should now definitely be correct.
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
4 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.
timeFieldNamewas missing from the response schema and so the public api call fails.Note, the data views page in stack management does not use this endpoint and considering this bug hasn't been noticed until now, I believe only external tools call this public endpoint.
Before
After
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*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.