Microsoft Teams Jira Cloud connector webhook issues

[Sean Lively]

We had several webhooks configured to only fire on specific transitions to the Jira Server connector in Teams, and that relied on a Atlassian provided translator at https://connectors.msteams-atlassian.com/JiraServer

The new Jira Cloud connector is successfully displaying messages from issue related events, but it won't display anything from a transition event. 

I captured the webhook data from a transition event, and sent it to Teams, and got a 400 response: "Webhook Bad Request - null or empty eventType"

Hopefully this gets the attention of someone on the product team, support has not been helpful.

[Jehan Bhathena]

Hi @Sean Lively 

I haven't had the chance to use the Teams integration on Jira Server, can you perhaps share the error or a few more details of what you're trying to capture with the webhook?

[Sean Lively]

The name of the old connector is misleading- it worked for both Jira Server and Jira Cloud, and we've never had on-prem Jira, only the cloud service.

We have webhooks configured to fire in several issue transitions. For instance, if a Helpdesk issue gets transitioned to an "Escalated to Dev" status, the webhook would send a message in a private teams channel alerting team leads something needs to be looked at.

Reproduction is easy- setup the Jira Cloud connector, and once you're getting issue events showing up in Teams, add the webhook to a transition.

You won't get an error message, as Atlassian doesn't expose the webhook logs, but you also won't get a message in teams from the transition. If you then redirect your webhooks to a testing site, you'll see that the Transition payload is different from the Event payload.

Resend the Event payload to your Teams url, and it'll show up in Teams. Resending the Transition payload will result in a 400 error: "Webhook Bad Request - null or empty eventType"

The Jira Cloud connector doesn't know how to display the Transition webhook, and it should be an easy update, but support has now spent 2 weeks dodging any kind acknowledgement this is a bug with the Jira Cloud connector.