[ResponseOps][Reporting] Add email cc, bcc, subject and message fields to scheduled reports email by umbopepato · Pull Request #242922 · elastic/kibana

umbopepato · 2025-11-13T14:52:29Z

📄 Summary

Adds new fields to the scheduled reports flyout form:
- cc and bcc recipients fields,
- subject and message with Mustache support
Makes the email fields editable for previously created schedules
Fixes some unit tests that were passing but were using a wrong format for scheduled reports sent to the form component
Adds unit tests and improve existing ones
Adds basic functional tests for scheduled reports flyout

🧪 Verification steps

✅ Happy Path

Configure a working default email connector in your kibana.yaml, i.e. a local mailhog instance:

notifications.connectors.default.email: email
xpack.actions.preconfigured:
  email:
    name: 'Default email connector'
    actionTypeId: '.email'
    config:
      service: other
      from: testsender@test.com
      host: 0.0.0.0
      port: 1025
      secure: false
      hasAuth: false

Schedule an export (i.e. of a Dashboard or Discover session)
In the flyout, select "Send by email"
Add at least one recipient
Add a subject and message, with variable interpolations
Wait for the export to be scheduled
In the email service you configured, check that the reported email contains the expected subject and message

⚡️ Edge Cases

Schedule an export with a non-existent variable in the email message. The resulting text should ignore the invalid variable.

❌ Failure Cases

Schedule an export with one or more syntax errors in the template. The resulting email messages should include a debug message for the user to correct the template.

📷 Screenshots

⏪ Backport rationale

Not backporting since this is a new functionality

🔗 References

Closes https://github.com/elastic/kibana-team/issues/2084

Release Notes

Adds new fields to the schedule export form email notification section: cc and bcc recipients, subject and message with Mustache templating support

☑️ Checklist

Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
(📝 Docs issue) Documentation was added for features that require explanation or tutorials
Unit or functional tests 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~~
~~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.~~
(⌛ running) Flaky Test Runner 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
Review the backport guidelines and apply applicable backport:* labels.

elasticmachine · 2025-11-17T16:36:44Z

Pinging @elastic/response-ops (Team:ResponseOps)

umbopepato · 2025-11-21T10:47:39Z

...form/plugins/private/reporting/public/management/components/create_scheduled_report_form.tsx

+          ? {
+              email: {
+                to: emailRecipients,
+                cc: emailCcRecipients,


The cc and bcc fields were already supported by the backend but not on the FE, added these too

umbopepato · 2025-11-21T11:10:48Z

...ck/platform/plugins/private/reporting/public/management/components/scheduled_report_form.tsx

    [http.basePath]
  );
  const { defaultTimezone } = useDefaultTimezone();
+  const hasCcBcc =


It seemed weird to be able to click the cc bcc toggle in editMode so I removed it and automatically showed the fields only if they have a value:

cc @tiamliu

Edit: now that those are editable I reenabled the Cc Bcc button, but kept the auto-show logic in edit mode for ease of use

umbopepato · 2025-11-21T11:11:29Z

x-pack/platform/plugins/private/reporting/public/management/validators/emails_validator.ts

  (
    validateEmailAddresses: ActionsPublicPluginSetup['validateEmailAddresses']
-  ): ValidationFunc<ScheduledReport, string, string> =>
+  ): ValidationFunc<Partial<ScheduledReport>, string, string> =>


Had to make this partial to avoid type errors with FormData being only a subset of ScheduledReport

kibanamachine · 2025-11-21T12:31:19Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9885

[❌] x-pack/platform/test/reporting_functional/reporting_and_security.config.ts: 0/50 tests passed.

see run history

kibanamachine · 2025-11-21T14:38:04Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9891

[❌] x-pack/platform/test/reporting_functional/reporting_and_security.config.ts: 0/50 tests passed.

see run history

cnasikas

I tested the whole end-to-end workflow, and it is working as expected! Are there any PM requirements where the email address, the text, and the subject cannot be changed for a user with full access? Same, for a user without the scheduled reporting feature privilege, but for the subject and the message.

cnasikas · 2025-11-21T14:03:52Z

...form/plugins/private/reporting/public/management/components/create_scheduled_report_form.tsx

Could you please add a test in x-pack/platform/plugins/private/reporting/public/management/components/create_scheduled_report_form.test.tsx for the new functionality?

I initially added some tests there, but I ended up writing some functional tests in disguise that took an absurd amount of time to run (I had to increase the timeout to 15 seconds to pass CI 🤯). After all this component is a thin wrapper on top of the form and I was testing well beyond its code, and since I did write some actual functional tests for the entire flyout experience in this PR, I switched to testing the actual code of this component and leave the entire flow to fn tests

Thanks, it makes sense to me!

...ck/platform/plugins/private/reporting/public/management/components/scheduled_report_form.tsx

joana-cps

Small nit in the scheduled form:

The space between fields it's too big. I think 8px is enough and we can also use16px if needed.
There's no need for the help text in the To field to be that long. Suggestion to change to: We'll also email the report to the addresses you specify here.
Example:

Subject and Message fields

Should we have a default text in the subject and message field? I know they are optional fields but I think would be a nice insentive to avoid empty subject and message all the time. cc: @nastasha-solomon
I would change the subject to required field, it's weird to allow it to send emails with empty subject and message. Might be tagged as spam right away.

joana-cps

I can still add variables in all the fields, even if they are disabled.

This might have been a product, prioritization decision, but why can't I change email fields when editing a schedule?
In this case I only added 1 email, and I'm a superuser. I should at least be able to disable the Send by email option. cc: @tiamliu @cnasikas

joana-cps

Currently, there are no deprecated variables here. Can we remove this until there is?

kibanamachine · 2025-11-21T17:12:54Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9892

[❌] x-pack/platform/test/reporting_functional/reporting_and_security.config.ts: 0/200 tests passed.

see run history

nastasha-solomon · 2025-11-24T15:27:51Z

Should we have a default text in the subject and message field? I know they are optional fields but I think would be a nice insentive to avoid empty subject and message all the time.

This is a great idea! Emails with empty subject lines and bodies could easily be ignored or end up in folk's spam folder.

umbopepato · 2025-11-25T15:56:08Z

The space between fields it's too big. I think 8px is enough and we can also use16px if needed.

There was an extra EuiFlexGroup which I now realize it's probably useless. Removing it just restored the natural EuiDescribedFormGroup children flow with margins, which should match your expectations. Let me know if it doesn't, and thanks for the heads up!

There's no need for the help text in the To field to be that long. Suggestion to change to: We'll also email the report to the addresses you specify here.

Agree, but I had to shorten variant that non-reporting-manager users see (they can only email to themselves so this field is disabled), hope it's fine!

Should we have a default text in the subject and message field? I know they are optional fields but I think would be a nice insentive to avoid empty subject and message all the time. cc: @nastasha-solomon

I would change the subject to required field, it's weird to allow it to send emails with empty subject and message. Might be tagged as spam right away.

About these last two points: email subject and message weren't editable before these couple of PRs and had a default hard-coded value, which we keep assigning as default values if the user doesn't set them. So we they do have default values, they're just not visible to the user right away from the UI. I used help texts and placeholders to clarify this and guide the user. We could pre-compile the two fields with the default values in the UI too, but we'd need to keep doing it in the backend regardless; idk how much sense does it make to do it everywhere.
Also, while writing these texts I realized that we weren't giving any clue to the user about Mustache and markdown, so I added a bit of guidance on that as well:

umbopepato · 2025-11-25T15:59:36Z

I can still add variables in all the fields, even if they are disabled.

Thanks again for finding this, I initially fixed it but...

This might have been a product, prioritization decision, but why can't I change email fields when editing a schedule?
In this case I only added 1 email, and I'm a superuser. I should at least be able to disable the Send by email option. cc: @tiamliu @cnasikas

... as you could tell from the external conversations on this last point, things have changed a bit and I now enabled editing of all email fields, so I reverted the fix 😂

umbopepato · 2025-11-25T16:00:43Z

Currently, there are no deprecated variables here. Can we remove this until there is?

I inherited this component from actions and didn't want to change it too much, but this is a fairly small change, so I just went ahead and did it. This might have a small impact in functional tests of actions, let's see what happens in CI 🤞

…reports-email-body-form

umbopepato · 2025-11-27T14:15:57Z

About these last two points: email subject and message weren't editable before these couple of PRs and had a default hard-coded value, which we keep assigning as default values if the user doesn't set them. So we they do have default values, they're just not visible to the user right away from the UI. I used help texts and placeholders to clarify this and guide the user. We could pre-compile the two fields with the default values in the UI too, but we'd need to keep doing it in the backend regardless; idk how much sense does it make to do it everywhere.
Also, while writing these texts I realized that we weren't giving any clue to the user about Mustache and markdown, so I added a bit of guidance on that as well:

We don't need to overcomplicate here. I suggest using the default texts that we already have and pre-filling the subject and the message fields. By doing that, we're already showing that it supports mustache and markdown (because we show it in our default message, no need for helper text). And as a plus, we're giving the user a starting point. win win 🙂

Let me or @nastasha-solomon know if there's any need to improve those defaults.

Done! The previous fallback values set by the backend weren't i18nalized so I took the occasion and created translations for them shared by both server and client 🙂

I left a bit of hint below the message textarea because there wasn't anything hinting to markdown support

umbopepato · 2025-11-27T14:34:44Z

...ackages/shared/response-ops/recurring-schedule-form/components/custom_recurring_schedule.tsx

                legend: 'Repeat on weekday',
                options: WEEKDAY_OPTIONS,
                isDisabled: readOnly,
+                ...(compressed ? { buttonSize: 'compressed' } : {}),


Form hook lib doesn't type these props objects so some of these compressed, isDisabled and readOnly props were passed the wrong way and ended up being passed to HTML elements, causing a lot of React error logs. All should be fixed now

umbopepato · 2025-11-27T14:37:15Z

x-pack/platform/plugins/private/reporting/common/translations.ts

+
+import { i18n } from '@kbn/i18n';
+
+export const SCHEDULED_REPORT_FORM_EMAIL_SUBJECT_DEFAULT_VALUE = i18n.translate(


These default subject and message texts were not translated in the backend so I added common versions for both FE and BE.
Read here to know more

umbopepato · 2025-11-27T14:40:30Z

...atform/plugins/private/reporting/public/management/components/scheduled_report_form.test.tsx

 jest.mock('../apis/get_reporting_health');

-const mockValidateEmailAddresses = jest.fn().mockResolvedValue([]);
+const mockValidateEmailAddresses = jest.fn().mockReturnValue([]);


The original fn is not async

umbopepato · 2025-11-27T14:40:40Z

...plugins/private/reporting/public/management/components/create_scheduled_report_form.test.tsx

 jest.mock('../apis/schedule_report');

-const mockValidateEmailAddresses = jest.fn().mockResolvedValue([]);
+const mockValidateEmailAddresses = jest.fn().mockReturnValue([]);


The original fn is not async

umbopepato · 2025-11-27T14:41:56Z

...atform/plugins/private/reporting/public/management/components/scheduled_report_form.test.tsx

-      renderWithProviders(<ScheduledReportForm {...props} />);
+  describe('when in readonly mode', () => {
+    it('disables title', async () => {
+      renderWithProviders(<ScheduledReportForm {...defaultProps} readOnly />);


Moved the props to the JSX el itself so they're typed

umbopepato · 2025-11-27T14:44:24Z

...server/routes/internal/scheduled_reports/integration_tests/scheduling_from_jobparams.test.ts

      .then(({ body }) =>
-        expect(body.message).toMatchInlineSnapshot(
-          `"[request body.notification.email.to]: could not parse array value from json input"`
+        expect(body.message).toEqual(


These somehow started failing even though the error message was exactly the same as the expected one. toEqual works though

kibanamachine · 2025-11-27T15:21:14Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9934

[❌] x-pack/platform/test/reporting_functional/reporting_and_security.config.ts: 44/50 tests passed.

see run history

cnasikas

LGTM! Tested and it is working fine! Thanks for the extra effort with the update.

cnasikas · 2025-11-27T16:10:11Z

src/platform/packages/shared/kbn-alerts-ui-shared/src/add_message_variables/index.tsx

nit: Let's add a small unit test to check that the deprecated button is hidden.

Oh right, added ✅

cnasikas · 2025-11-27T16:13:09Z

x-pack/platform/plugins/private/reporting/common/translations.ts

+  {
+    defaultMessage: 'Your scheduled report is attached for you to download or share.',
+    description:
+      'The curly braces are Mustache interpolations, not translation variables, hence the single quotes around them.',


nit: There are no interpolations in the message. Should we remove this?

Oh right thanks for the heads up!

cnasikas · 2025-11-27T16:14:31Z

...form/plugins/private/reporting/public/management/components/create_scheduled_report_form.tsx

Thanks, it makes sense to me!

cnasikas · 2025-11-27T16:25:48Z

...form/plugins/private/reporting/public/management/components/edit_scheduled_report_flyout.tsx

        title,
        schedule: { rrule: rrule as Rrule },
+        notification: {
+          email: sendByEmail


Yes, this is how ES works. Setting to null is the only option.

…vent

…reports-email-body-form

kibanamachine · 2025-11-27T19:38:10Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9936

[❌] x-pack/platform/test/reporting_functional/reporting_and_security.config.ts: 171/200 tests passed.

see run history

…reports-email-body-form

kibanamachine · 2025-11-28T12:41:37Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9943

[❌] x-pack/platform/test/reporting_functional/reporting_and_security.config.ts: 174/200 tests passed.

see run history

…reports-email-body-form

kibanamachine · 2025-11-28T14:25:59Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9947

[❌] x-pack/platform/test/reporting_functional/reporting_and_security.config.ts: 73/100 tests passed.

see run history

elasticmachine · 2025-11-28T16:29:26Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: 5fa6dc0

Failed CI Steps

Test Failures

[job] [logs] FTR Configs #147 / ObservabilityApp Custom threshold rule with ad-hoc data view should create a custom threshold rule with an ad-hoc data view
[job] [logs] FTR Configs #76 / serverless search UI - search features Search Playground - Saved Playgrounds Update Saved Playground should allow updating playground name

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`reporting`	237	239	+2

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`triggersActionsUi`	502	504	+2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`alerting`	88.4KB	88.5KB	+44.0B
`reporting`	138.2KB	143.9KB	+5.7KB
total			+5.7KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
`reporting`	41.4KB	41.6KB	+146.0B
`triggersActionsUi`	106.7KB	107.0KB	+293.0B
total			+439.0B

Unknown metric groups

API count

id	before	after	diff
`triggersActionsUi`	506	508	+2

ESLint disabled line counts

id	before	after	diff
`@kbn/test-suites-xpack-platform`	161	162	+1

Total ESLint disabled count

id	before	after	diff
`@kbn/test-suites-xpack-platform`	171	172	+1

History

💔 Build #366733 failed a675709
💚 Build #366268 succeeded fb7d8b9
💔 Build #365792 failed dcaa78a
💔 Build #365289 failed 5bfd1d9
💔 Build #365180 failed 17ac8fd
💔 Build #363737 failed 5914b86

…s to scheduled reports email (elastic#242922) ## 📄 Summary - Adds new fields to the scheduled reports flyout form: - cc and bcc recipients fields, - subject and message with Mustache support - Makes the email fields editable for previously created schedules - Fixes some unit tests that were passing but were using a wrong format for scheduled reports sent to the form component - Adds unit tests and improve existing ones - Adds basic functional tests for scheduled reports flyout <details> <summary> ## 🧪 Verification steps </summary> ### ✅ Happy Path 1. Configure a working default email connector in your kibana.yaml, i.e. a local mailhog instance: ```yaml notifications.connectors.default.email: email xpack.actions.preconfigured: email: name: 'Default email connector' actionTypeId: '.email' config: service: other from: testsender@test.com host: 0.0.0.0 port: 1025 secure: false hasAuth: false ``` 2. Schedule an export (i.e. of a Dashboard or Discover session) 3. In the flyout, select "Send by email" 4. Add at least one recipient 5. Add a subject and message, with variable interpolations 6. Wait for the export to be scheduled 7. In the email service you configured, check that the reported email contains the expected subject and message ### ⚡️ Edge Cases Schedule an export with a non-existent variable in the email message. The resulting text should ignore the invalid variable. ### ❌ Failure Cases Schedule an export with one or more syntax errors in the template. The resulting email messages should include a debug message for the user to correct the template. </details> <details> <summary> ## 📷 Screenshots </summary> <img width="595" height="1066" alt="image" src="https://github.com/user-attachments/assets/2ffecd32-70f4-4b9d-81a1-647d733ce297" /> </details> ## ⏪ Backport rationale Not backporting since this is a new functionality ## 🔗 References Closes elastic/kibana-team#2084 ## Release Notes Adds new fields to the schedule export form email notification section: cc and bcc recipients, subject and message with Mustache templating support ## ☑️ 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/src/platform/packages/shared/kbn-i18n/README.md) - [ ] (📝 [Docs issue](elastic/docs-content#4027)) [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)~~ - [ ] ~~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.~~ - [ ] (⌛ [running](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/9934/steps/canvas)) [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) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

umbopepato added backport:skip This PR does not require backporting Team:ResponseOps Platform ResponseOps team (formerly the Cases and Alerting teams) t// release_note:feature Makes this part of the condensed release notes v9.3.0 labels Nov 13, 2025

umbopepato force-pushed the 2084-scheduled-reports-email-body-form branch from 3eb4780 to a91dfac Compare November 17, 2025 10:50

umbopepato marked this pull request as ready for review November 17, 2025 16:36

umbopepato requested a review from a team as a code owner November 17, 2025 16:36

umbopepato force-pushed the 2084-scheduled-reports-email-body-form branch from a91dfac to 1427b87 Compare November 21, 2025 10:40

umbopepato commented Nov 21, 2025

View reviewed changes

umbopepato requested a review from joana-cps November 21, 2025 11:15

umbopepato mentioned this pull request Nov 21, 2025

[Internal][ResponseOps][Reporting]: Scheduled reports new email fields and Mustache support elastic/docs-content#4027

Closed

cnasikas reviewed Nov 21, 2025

View reviewed changes

joana-cps reviewed Nov 21, 2025

View reviewed changes

elastic-vault-github-plugin-prod bot requested a review from a team as a code owner November 25, 2025 15:20

umbopepato requested review from a team as code owners November 25, 2025 16:46

umbopepato added 3 commits November 27, 2025 11:55

Merge branch 'main' of github.com:elastic/kibana into 2084-scheduled-…

fb7d8b9

…reports-email-body-form

Improve tests

7a0dd65

Merge branch 'main' of github.com:elastic/kibana into 2084-scheduled-…

dcb35d4

…reports-email-body-form

umbopepato commented Nov 27, 2025

View reviewed changes

cnasikas approved these changes Nov 27, 2025

View reviewed changes

umbopepato added 3 commits November 27, 2025 19:34

Add variables picker test for deprecated vars footer, update to userE…

4d568b4

…vent

Merge branch 'main' of github.com:elastic/kibana into 2084-scheduled-…

a3c264d

…reports-email-body-form

Remove unnecessary translation description

48b5ebc

umbopepato added 2 commits November 28, 2025 12:56

Merge branch 'main' of github.com:elastic/kibana into 2084-scheduled-…

38dfd27

…reports-email-body-form

Flaky fn test fix attempt

d53404b

umbopepato added 4 commits November 28, 2025 13:45

Flaky fn test fix attempt

7d9a44c

Merge branch 'main' of github.com:elastic/kibana into 2084-scheduled-…

a675709

…reports-email-body-form

Skip flaky fn tests

1574f78

Merge branch 'main' of github.com:elastic/kibana into 2084-scheduled-…

5fa6dc0

…reports-email-body-form

umbopepato enabled auto-merge (squash) November 28, 2025 14:18

umbopepato merged commit f08de60 into elastic:main Nov 28, 2025
13 checks passed


		import { i18n } from '@kbn/i18n';

		export const SCHEDULED_REPORT_FORM_EMAIL_SUBJECT_DEFAULT_VALUE = i18n.translate(

Conversation

umbopepato commented Nov 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📄 Summary

🧪 Verification steps

✅ Happy Path

⚡️ Edge Cases

❌ Failure Cases

📷 Screenshots

⏪ Backport rationale

🔗 References

Release Notes

☑️ Checklist

elasticmachine commented Nov 17, 2025

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kibanamachine commented Nov 21, 2025

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9885

kibanamachine commented Nov 21, 2025

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9891

cnasikas left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

joana-cps left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Subject and Message fields

joana-cps left a comment

Choose a reason for hiding this comment

joana-cps left a comment

Choose a reason for hiding this comment

kibanamachine commented Nov 21, 2025

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9892

nastasha-solomon commented Nov 24, 2025

umbopepato commented Nov 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

umbopepato commented Nov 25, 2025

umbopepato commented Nov 25, 2025

umbopepato commented Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

umbopepato Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

umbopepato Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

umbopepato Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kibanamachine commented Nov 27, 2025

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9934

cnasikas left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

umbopepato Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kibanamachine commented Nov 27, 2025

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#9936

kibanamachine commented Nov 28, 2025

Flaky Test Runner Stats

umbopepato commented Nov 13, 2025 •

edited

Loading

joana-cps left a comment •

edited

Loading

umbopepato commented Nov 25, 2025 •

edited

Loading

umbopepato commented Nov 27, 2025 •

edited

Loading

umbopepato Nov 27, 2025 •

edited

Loading

umbopepato Nov 27, 2025 •

edited

Loading

umbopepato Nov 27, 2025 •

edited

Loading

umbopepato Nov 27, 2025 •

edited

Loading