Adding an alert variable in PagerDuty action and selecting a value results in an extra space character

[romain-chanu]

Kibana version: Affects both 7.7.0 and 7.7.1

Elasticsearch version: Affects both 7.7.0 and 7.7.1

Server OS version: MacOS Mojave 10.14.6

Browser version: Chrome Version 83.0.4103.61 (Official Build) (64-bit)

Original install method (e.g. download page, yum, from source, etc.): MAC (tarball packages)

Describe the bug: When adding an alert variable in PagerDuty action and selecting a value from the list, this results in an extra character leading the alert variable value.

Steps to reproduce:

1. Create an alert and add a PagerDuty action.
2. Click Add alert variable for any of the related configuration properties.
3. Select a value from the list
4. Observe the extra space character leading the alert variable value.

Additional notes:

In Kibana 7.7.0, selecting {{context.date}} in the timestamp property will result in a parsing error (because of the extra space character). Error message in Kibana: Error: error validating action params: error parsing timestamp. Same error if the timestamp property is empty.

In Kibana 7.7.1, such parsing error should not happen (fixed in #63954 ?). However, adding an alert variable and selecting a value from the list still results in the extra space character.

Expected behavior: No extra space character should be added when selecting an alert variable value.

Related Github issues:

• PagerDuty incidents are not created when using the Elastic Alerts Integration Type #68065
• [SIEM] PagerDuty timestamp causes rule to fail #64871

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)