Your window into the Elastic Stack
Find a file
Kibana Machine e0cc912c80
[8.8] [ResponseOps][Maintenance Windows] Show dates in the selected timezone on the edit form (#158020) (#158075)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ResponseOps][Maintenance Windows] Show dates in the selected
timezone on the edit form
(#158020)](https://github.com/elastic/kibana/pull/158020)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Alexi
Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-18T12:10:38Z","message":"[ResponseOps][Maintenance
Windows] Show dates in the selected timezone on the edit form
(#158020)\n\nResolves
https://github.com/elastic/kibana/issues/158013\r\n\r\n##
Summary\r\n\r\nWhen a specific timezone has been set for a schedule, we
will convert\r\nthe time to local time when showing it in a list, table
or overview.\r\nUpdated the edit/create form so that when someone
chooses to edit that\r\nschedule, we will then default to and show the
specific timezone that\r\nwas selected when it was
created.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n\r\n### To
verify\r\nScenario 1: \r\n\r\n1. Make sure your kibana timezone setting
is set to `'Browser'`\r\n2. Create a maintenance window and set the
timezone to\r\n`America/Los_Angeles` or any timezone that is not your
own\r\n3. Verify that the times match the timezone set and save
<img\r\nwidth=\"1002\" alt=\"Screen Shot 2023-05-17 at 2 47 12
PM\"\r\nsrc=\"4ea15e09-3482-42a5-aa06-2dee7dd8c189\">\r\n4.
Verify on the table that the times match your current timezone
<img\r\nwidth=\"829\" alt=\"Screen Shot 2023-05-17 at 2 51 31
PM\"\r\nsrc=\"29e6f52b-8c40-4133-92fe-0674400a7368\">\r\n5.
Edit and verify that the times match the timezone you set when the
mw\r\nwas created <img width=\"991\" alt=\"Screen Shot 2023-05-17 at 2
52 29
PM\"\r\nsrc=\"9920d569-0e7d-484a-8f08-d5f38a94616d\">\r\n\r\nScenario
2: \r\n\r\n1. Make sure your kibana timezone setting is set to timezone.
I used\r\n`America/Denver`\r\n2. Create a maintenance window and verify
that the times reflect the\r\ntimezone set in adv settings <img
width=\"1000\" alt=\"Screen Shot\r\n2023-05-17 at 2 55 26
PM\"\r\nsrc=\"31f3164e-bb48-4ebe-98db-9bb24254fcd5\">\r\n3.
Verify on the table that the times match adv settings\r\n4. Edit and
verify that the times and the timezone match adv settings\r\n<img
width=\"1001\" alt=\"Screen Shot 2023-05-17 at 2 56 00
PM\"\r\nsrc=\"350ad4bb-9dbb-4265-bd7a-cf6a0cace7f7\">","sha":"212e4df02d91d95f2ab574216fcedbe2c4a09552","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v8.8.0","v8.9.0"],"number":158020,"url":"https://github.com/elastic/kibana/pull/158020","mergeCommit":{"message":"[ResponseOps][Maintenance
Windows] Show dates in the selected timezone on the edit form
(#158020)\n\nResolves
https://github.com/elastic/kibana/issues/158013\r\n\r\n##
Summary\r\n\r\nWhen a specific timezone has been set for a schedule, we
will convert\r\nthe time to local time when showing it in a list, table
or overview.\r\nUpdated the edit/create form so that when someone
chooses to edit that\r\nschedule, we will then default to and show the
specific timezone that\r\nwas selected when it was
created.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n\r\n### To
verify\r\nScenario 1: \r\n\r\n1. Make sure your kibana timezone setting
is set to `'Browser'`\r\n2. Create a maintenance window and set the
timezone to\r\n`America/Los_Angeles` or any timezone that is not your
own\r\n3. Verify that the times match the timezone set and save
<img\r\nwidth=\"1002\" alt=\"Screen Shot 2023-05-17 at 2 47 12
PM\"\r\nsrc=\"4ea15e09-3482-42a5-aa06-2dee7dd8c189\">\r\n4.
Verify on the table that the times match your current timezone
<img\r\nwidth=\"829\" alt=\"Screen Shot 2023-05-17 at 2 51 31
PM\"\r\nsrc=\"29e6f52b-8c40-4133-92fe-0674400a7368\">\r\n5.
Edit and verify that the times match the timezone you set when the
mw\r\nwas created <img width=\"991\" alt=\"Screen Shot 2023-05-17 at 2
52 29
PM\"\r\nsrc=\"9920d569-0e7d-484a-8f08-d5f38a94616d\">\r\n\r\nScenario
2: \r\n\r\n1. Make sure your kibana timezone setting is set to timezone.
I used\r\n`America/Denver`\r\n2. Create a maintenance window and verify
that the times reflect the\r\ntimezone set in adv settings <img
width=\"1000\" alt=\"Screen Shot\r\n2023-05-17 at 2 55 26
PM\"\r\nsrc=\"31f3164e-bb48-4ebe-98db-9bb24254fcd5\">\r\n3.
Verify on the table that the times match adv settings\r\n4. Edit and
verify that the times and the timezone match adv settings\r\n<img
width=\"1001\" alt=\"Screen Shot 2023-05-17 at 2 56 00
PM\"\r\nsrc=\"350ad4bb-9dbb-4265-bd7a-cf6a0cace7f7\">","sha":"212e4df02d91d95f2ab574216fcedbe2c4a09552"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158020","number":158020,"mergeCommit":{"message":"[ResponseOps][Maintenance
Windows] Show dates in the selected timezone on the edit form
(#158020)\n\nResolves
https://github.com/elastic/kibana/issues/158013\r\n\r\n##
Summary\r\n\r\nWhen a specific timezone has been set for a schedule, we
will convert\r\nthe time to local time when showing it in a list, table
or overview.\r\nUpdated the edit/create form so that when someone
chooses to edit that\r\nschedule, we will then default to and show the
specific timezone that\r\nwas selected when it was
created.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n\r\n### To
verify\r\nScenario 1: \r\n\r\n1. Make sure your kibana timezone setting
is set to `'Browser'`\r\n2. Create a maintenance window and set the
timezone to\r\n`America/Los_Angeles` or any timezone that is not your
own\r\n3. Verify that the times match the timezone set and save
<img\r\nwidth=\"1002\" alt=\"Screen Shot 2023-05-17 at 2 47 12
PM\"\r\nsrc=\"4ea15e09-3482-42a5-aa06-2dee7dd8c189\">\r\n4.
Verify on the table that the times match your current timezone
<img\r\nwidth=\"829\" alt=\"Screen Shot 2023-05-17 at 2 51 31
PM\"\r\nsrc=\"29e6f52b-8c40-4133-92fe-0674400a7368\">\r\n5.
Edit and verify that the times match the timezone you set when the
mw\r\nwas created <img width=\"991\" alt=\"Screen Shot 2023-05-17 at 2
52 29
PM\"\r\nsrc=\"9920d569-0e7d-484a-8f08-d5f38a94616d\">\r\n\r\nScenario
2: \r\n\r\n1. Make sure your kibana timezone setting is set to timezone.
I used\r\n`America/Denver`\r\n2. Create a maintenance window and verify
that the times reflect the\r\ntimezone set in adv settings <img
width=\"1000\" alt=\"Screen Shot\r\n2023-05-17 at 2 55 26
PM\"\r\nsrc=\"31f3164e-bb48-4ebe-98db-9bb24254fcd5\">\r\n3.
Verify on the table that the times match adv settings\r\n4. Edit and
verify that the times and the timezone match adv settings\r\n<img
width=\"1001\" alt=\"Screen Shot 2023-05-17 at 2 56 00
PM\"\r\nsrc=\"350ad4bb-9dbb-4265-bd7a-cf6a0cace7f7\">","sha":"212e4df02d91d95f2ab574216fcedbe2c4a09552"}}]}]
BACKPORT-->

Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>
2023-05-18 07:14:26 -07:00
.buildkite [8.8] [functional tests] split fleet_api_integration config into smaller ones (#156407) (#156559) 2023-05-03 08:33:03 -07:00
.ci Upgrade Node.js to 16.19.1 (#151527) 2023-02-21 10:40:59 -06:00
.github chore(NA): remove codeowners and update branch property after branch cut 2023-04-26 16:24:35 +01:00
api_docs [api-docs] 2023-04-26 Daily api_docs build (#155820) 2023-04-26 00:59:36 -04:00
config [8.8] [Serverless] Select project type via config (#155754) (#155997) 2023-04-27 08:19:35 -07:00
dev_docs [8.8] [performance] enable journey run against cloud deployments (#156720) (#157123) 2023-05-08 21:46:16 -07:00
docs [8.8] [DOCS] Add api_key_created_by_user to alerting API specification (#158018) (#158037) 2023-05-17 17:12:56 -07:00
examples [8.8] [Search Sessions] Fix flaky partial results test in search examples (#155816) (#156125) 2023-04-27 17:34:02 -07:00
kbn_pm chore(NA): exit early with link for docs when using kbn_pm on windows (#139745) 2023-02-10 15:38:29 +00:00
legacy_rfcs rename @elastic/* packages to @kbn/* (#138957) 2022-08-18 08:54:42 -07:00
licenses
packages [8.8] [DOCS] Maintenance windows (#157806) (#158019) 2023-05-17 14:55:05 -07:00
plugins
scripts [ci] build next docs in PRs when relevant files change (#149991) 2023-02-09 21:57:10 -07:00
src [8.8] [Controls] Add query settings to ES query (#157923) (#158023) 2023-05-17 13:03:47 -07:00
test [8.8] Update ftr services to handle occasional WebDriverError (#157283) (#157326) 2023-05-10 13:50:57 -07:00
typings Wrap rison-node to improve types (#146649) 2022-12-01 08:33:56 -07:00
vars [ts] ts refs cache was removed, remove capture task 2022-10-28 14:27:18 -05:00
x-pack [8.8] [ResponseOps][Maintenance Windows] Show dates in the selected timezone on the edit form (#158020) (#158075) 2023-05-18 07:14:26 -07:00
.backportrc.json chore(NA): adds 8.7 into backportrc (#150569) 2023-02-08 21:22:43 +00:00
.bazelignore Bazel config maintenance (#135442) 2022-07-05 10:20:26 -05:00
.bazeliskversion
.bazelrc chore(NA): use new and more performant BuildBuddy servers (#130350) 2022-04-18 02:01:38 +01:00
.bazelrc.common Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
.bazelversion chore(NA): revert bazel upgrade for v5.2.0 (#135096) 2022-06-24 03:57:21 +01:00
.browserslistrc
.editorconfig
.eslintignore [NOTICE.txt] Fix notices for Gainsight and FullStory (#146004) 2023-01-13 14:49:43 +01:00
.eslintrc.js [SecuritySolution] Refactor security packages (#155365) 2023-04-26 05:05:36 -07:00
.gitattributes
.gitignore [packages] migrate all plugins to packages (#148130) 2023-02-08 21:06:50 -06:00
.i18nrc.json [SecuritySolution] Refactor security packages (#155365) 2023-04-26 05:05:36 -07:00
.node-version Upgrade Node.js to 16.19.1 (#151527) 2023-02-21 10:40:59 -06:00
.npmrc
.nvmrc Upgrade Node.js to 16.19.1 (#151527) 2023-02-21 10:40:59 -06:00
.prettierignore
.prettierrc
.stylelintignore
.stylelintrc Bump stylelint to ^14 (#136693) 2022-07-20 10:11:00 -05:00
.telemetryrc.json [Telemetry] Fix telemetry-tools TS parser for packages (#149819) 2023-01-31 04:09:09 +03:00
.yarnrc
BUILD.bazel Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
FAQ.md Fix small typos in the root md files (#134609) 2022-06-23 09:36:11 -05:00
fleet_packages.json [8.8] Sync bundled packages with Package Storage (#157953) 2023-05-17 08:27:50 +02:00
github_checks_reporter.json
Jenkinsfile
kibana.d.ts
LICENSE.txt
nav-kibana-dev.docnav.json Add March 2023 Newsletter link (#154248) 2023-04-06 16:04:06 -04:00
NOTICE.txt [FullStory] Update snippet (#153570) 2023-04-18 04:06:05 -07:00
package.json [8.8] [Enterprise Search] update search-ui + remove searchable-fields config (#157209) (#157244) 2023-05-10 02:52:58 -07:00
preinstall_check.js
README.md
renovate.json Session view and k8s dashboard fixes (#154982) 2023-04-17 16:22:28 -07:00
RISK_MATRIX.mdx
SECURITY.md
STYLEGUIDE.mdx [styleguide] update path to scss theme (#140742) 2022-09-15 10:41:14 -04:00
tsconfig.base.json [SecuritySolution] Refactor security packages (#155365) 2023-04-26 05:05:36 -07:00
tsconfig.browser.json
tsconfig.browser_bazel.json
tsconfig.json Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
TYPESCRIPT.md Fix small typos in the root md files (#134609) 2022-06-23 09:36:11 -05:00
versions.json chore(NA): update versions after v8.7.1 bump (#154029) 2023-03-30 16:11:53 +01:00
WORKSPACE.bazel Upgrade Node.js to 16.19.1 (#151527) 2023-02-21 10:40:59 -06:00
yarn.lock [8.8] [Enterprise Search] update search-ui + remove searchable-fields config (#157209) (#157244) 2023-05-10 02:52:58 -07:00

Kibana

Kibana is your window into the Elastic Stack. Specifically, it's a browser-based analytics and search dashboard for Elasticsearch.

Getting Started

If you just want to try Kibana out, check out the Elastic Stack Getting Started Page to give it a whirl.

If you're interested in diving a bit deeper and getting a taste of Kibana's capabilities, head over to the Kibana Getting Started Page.

Using a Kibana Release

If you want to use a Kibana release in production, give it a test run, or just play around:

Building and Running Kibana, and/or Contributing Code

You might want to build Kibana locally to contribute some code, test out the latest features, or try out an open PR:

Documentation

Visit Elastic.co for the full Kibana documentation.

For information about building the documentation, see the README in elastic/docs.

Version Compatibility with Elasticsearch

Ideally, you should be running Elasticsearch and Kibana with matching version numbers. If your Elasticsearch has an older version number or a newer major number than Kibana, then Kibana will fail to run. If Elasticsearch has a newer minor or patch number than Kibana, then the Kibana Server will log a warning.

Note: The version numbers below are only examples, meant to illustrate the relationships between different types of version numbers.

Situation Example Kibana version Example ES version Outcome
Versions are the same. 7.15.1 7.15.1 💚 OK
ES patch number is newer. 7.15.0 7.15.1 ⚠️ Logged warning
ES minor number is newer. 7.14.2 7.15.0 ⚠️ Logged warning
ES major number is newer. 7.15.1 8.0.0 🚫 Fatal error
ES patch number is older. 7.15.1 7.15.0 ⚠️ Logged warning
ES minor number is older. 7.15.1 7.14.2 🚫 Fatal error
ES major number is older. 8.0.0 7.15.1 🚫 Fatal error

Questions? Problems? Suggestions?

  • If you've found a bug or want to request a feature, please create a GitHub Issue. Please check to make sure someone else hasn't already created an issue for the same topic.
  • Need help using Kibana? Ask away on our Kibana Discuss Forum and a fellow community member or Elastic engineer will be glad to help you out.