/escalate "Team to notify" Slack Dropdown Broken - Always Selects the First Team

[ESNewmanium]

What went wrong?

What happened:

• When using the /escalate command in Slack, users are presented with a "Create Escalation" menu. In my setup there are 3 teams available for Direct Paging in the dropdown box for "Team to notify." Regardless of the selection made, the escalation always gets forced back to the first team in the list. The escalation is indeed sent to that team every time, so it isn't only an illusion of the UI.

What did you expect to happen:

• Selecting a "Team to notify" in the dropdown box should select that team. It instead automatically reverts to the first team in the list regardless of the selection input.

(In screenshots below you can see that there are 3 teams. Selecting anything other than "DBA" still reverts the selection to "DBA" immediately)

How do we reproduce it?

1. Create 2 or more Teams in Grafana.
2. Create a Direct Paging integration for each of the teams.
3. Run the /escalate command from Slack.
4. Attempt to select a "Team to notify." Observe if the dropdown box suddenly reverts to a different item.
5. Click "Create" and see if the escalation was actually routed to the intended team.

Grafana OnCall Version

v.1.3.59

Product Area

Chatops

Grafana OnCall Platform?

Kubernetes

User's Browser?

Slack Production 4.35.126

Anything else to add?

No response

[ESNewmanium]

I can also add that this broke somewhere between 1.3.47 and 1.3.55. I confirmed this bug present in 1.3.55 and no longer present as far back as 1.3.47.

Another thing to note: since these changes to the /escalate dialog there is no longer an Alert Group "Title" field. This is kinda handy to have because the new dialog creates a generic Alert Group title that would be much more useful if it were descriptive (e.g. "API is DOWN!!!" is a lot different to read at 3am than "Kevin is inviting you to join an escalation")

Alerts w/o Title get a generic description:

Old Alert Group dialog w/ title:

[ESNewmanium]

Somewhere between v.1.3.59 and v1.3.92 this is fixed. Closing.