MS Teams Connector for Jira DC doesn't work with new Teams

Issue Summary

In March 2023, Microsoft launched the "new Teams" client refresh. Since March 31, 2024, all users were automatically switched to the new interface (New Microsoft Teams).

The Microsoft Teams for Jira Server integration includes a channel connector that relies on a Jira DC webhook to notify members of issue creation/updates.

Attempting to add a new channel connector in the "new Teams" interface results in visual glitches. Even if successful, the webhook will receive 400 responses from the relay endpoint and messages will not appear in the Teams channel.

Steps to Reproduce

1. Switch to the "new Teams" and create a new channel.
2. Add the "Jira Server" channel connector (from manage channel).
3. Follow the prompts to add the webhook to Jira DC and save the connector.

Expected Results

The connector successfully saves and relays notifications to the channel.

Actual Results

Teams client

1. During setup, the integration states:

   You're setting up a connector for channel: undefined
   

   

1. After clicking save, the configured tab displays no configured connectors.
   
2. Switching back to the "old Teams" displays the connector, but the channel name is still "undefined"
   

Jira DC

The webhook endpoint receives 400 responses. The following is logged to atlassian-jira.log:

2024-04-18 00:00:00,000+0000 I/O dispatcher 1 DEBUG [o.apache.http.headers] http-outgoing-0 >> POST /JiraServer/a0261c5f... HTTP/1.1
2024-04-18 00:00:00,000+0000 I/O dispatcher 1 DEBUG [o.apache.http.headers] http-outgoing-0 >> Host: connectors.msteams-atlassian.com
[...]
2024-04-18 00:00:00,000+0000 I/O dispatcher 1 DEBUG [o.apache.http.headers] http-outgoing-0 << HTTP/1.1 400 Bad Request
2024-04-18 00:00:00,000+0000 I/O dispatcher 1 DEBUG [o.apache.http.wire] http-outgoing-0 << "Failed to handle notification"
2024-04-18 00:00:00,000+0000 httpclient-callbacks:thread-1 WARN anonymous [c.a.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Error - 400 when posting to web hook at 'https://connectors.msteams-atlassian.com/JiraServer/a0261c5f...'

Workaround

Workaround 1

1. Configure the new Jira Server Connector connection within the desired Teams channel. Do not copy the URL from the instruction; simply save the configuration and close the dialog.
2. Open the configured connectors for the channel and locate the most recently created Jira Server configuration. Click the manage button.
3. Copy the URL from the instructions and follow the provided steps.
4. Close the configuration by clicking the cancel button. Avoid using the save button, as it will generate a new configuration due to this bug.
5. Ensure that all new Jira notification cards are sent to the selected channel.

Workaround 2

Revert to the "old Teams" from the dropdown ([...]) to the left of your profile picture. Note that your org's Teams administrators may require all users to use the "new Teams" interface.