Watcher UI cannot be opened due to watches without a 'to' field in a slack message

[spinscale]

Kibana version: 6.3.1

Elasticsearch version: 6.3.1

If a user has configured a slack account in the YAML configuration that contains a default to field, then the slack message itself does not require to have a to field. However the watcher UI is not accessible at all when such a field is found.

The only way to get out of this is to edit the watch in dev-tools again.

Reproduce

Configure Elasticsearch

YAML configuration

xpack.notification.slack:
  account:
    monitoring:
      message_defaults:
        to: '#watcher-test'

Add slack hook URL to keystore

./elasticsearch-6.3.1/bin/elasticsearch-keystore add xpack.notification.slack.account.monitoring.secure_url

Start Elasticsearch and Kibana

Create this totally valid watch in devtools

PUT _xpack/watcher/watch/my_test_watch
{
  "trigger": {
    "schedule": {
      "interval": "10h"
    }
  },
  "input": {
    "simple": {}
  },
  "actions": {
    "the_slack_action": {
      "slack": {
        "message": {
          "text": "This is a test"
        }
      }
    }
  }
}

# execute to see the text in slack
POST _xpack/watcher/watch/my_test_watch/_execute

Now go to Management -> Watcher and see this error message and also the issue of not being able to use the watcher UI at all anymore.

The only workaround right now is to add a to field to the watch.

The offending code seems to be here

[spinscale]

are there any plans to work on this, as this can be an annoying issue for users leaving the watcher UI in an unusable state.

[bmcconaghy]

this was missing Management label and this escaped our attention @spinscale . We will try to work on it ASAP.

[mattkime]

Very similar to #23887 - seems a similar solution should work.

[sebelga]

This has been resolved in PR #23887