Default field in PagerDuty action isn't actually applied

[gmmorris]

Customer reported that their alerts that had "Critical" severity weren't paging us because when they land in Pagerduty they somehow became "info" severity. They noticed that in Kibana, if they click on the severity box and click on Critical (while it already says Critical by default), the alert would work correctly. So when they explicitly change the severity to error or critical it would have the correct behavior. It's only when they create an alert and leave it with the default severity (which is "Critical") that this would happen. If they click on severity then click on Critical (the exact same thing as the default) then the alert would behave correctly.

I was able to reproduce this on Main.
All you have to do is add a PagerDuty action to an alert and leave the Severity field on its default value.
The default says "Ciritcal", but in practice it sets it to "Info"/

[elasticmachine]

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