Create Teams chat or meeting gives Error server response: 422

[Leigh Elliott]

Hi Everyone,

I setup Microsoft Teams chat and meeting integration for JSM incident issue types today and once all of the integration and app approvals were completed I was able to get JSM and Microsoft Teams to connect.

However, when selecting the "Create chat or meeting" link on an incident and then setting i[ a chat and pressing "Create" the create button spins for a little while and then comes back with "Error server response: 422".  See screenshot below.

Has anyone else experienced this error and if so were you able to resolve?

  

[Leigh Elliott]

I revisited this today, and after resetting the MS Team configuration within the project settings, both Chats and Meetings worked. I no longer get the 422 error.

It's been about a year and a half since I first raised this, so I don't know what changed to fix it. Atlassian may have released multiple code fixes since then.  

[Yatish Madhav]

Thanks very much @Leigh Elliott - please can you share the details/steps under the project settings that you reconfigured? Thank you

[Leigh Elliott]

Hi Yatish, I followed this guide: https://support.atlassian.com/jira-service-management-cloud/docs/set-up-chat-in-microsoft-teams/ 

[Yatish Madhav]

Thanks @Leigh Elliott  - is there any specific section I should go through? I tried "Set up chat in your service project" and then when I connect the Assist Bot - it seems to be doing nothing.

OR there is some waiting I need to do?

Any help would be greatly appreciated. Thank you

[Yatish Madhav]

Hi all - I am not sure if I missed it. But how do we fix this? I tried to createa a Chat with a name of the issue key and a description with just numbers but it gives the 422 error. Thank you in advance

[Leigh Elliott]

I raised a support case with Atlassian Support for this error.  After investigation, they have referred me to a known bug: https://jira.atlassian.com/browse/JSDCLOUD-12457

[Leigh Elliott]

Sorry, I should clarify the issue is not resolved for me, and it would appear that, in my case, it is due to the bug mentioned above.

[Leigh Elliott]

The bug does explain the following Known criteria/limitations with MS teams

• Atlassian Account & MS Chat email ID must be same
• Must have between 3 ~ 20 participants
• Must not use special characters in chat topic ie:

  ~ # % & * { } + / \ : < > ? | ' "

  But in my case, none of the above criteria is applicable.  I did raise this with Atlassian Support, and they could not explain why.

[Jason Walker]

Hi all who have this issue, i have received an update from Atlassian on this. They have completed a fix, i have tested this in my environment and this is working. 
Hopefully its resolved for all impacted. 

[Leigh Elliott]

Thanks Jason.  I tested it again this morning, and it is still not working within our tenancy.

[Jason Walker]

Hey Leigh, i tested again this morning and it is working for me, the follow up issue i have now though is that the users are not added to the chat. 

I have raised a new ticket for this. 

Hoping it will start working for you soon if this is a deployment delay :O 

[Rachel Wright]

Hi @Leigh Elliott and @Jason Walker

I'm sorry, I don't know the answer to your question but I'm not sure others in the community will either. Since it's a server error, I'd recommend creating a bug issue for Atlassian. 

To log your bug, visit: https://jira.atlassian.com/browse/API I'd probably file this in the API project or the JSDCLOUD project. I did some hunting in there and didn't see any existing issues referencing error 422 and Teams.

If you've installed a third party connector app from the Atlassian Marketplace, then you'll need to contact that vendor for support, of course.

You're not the only one who's experienced this. I found this issue here as well: https://community.atlassian.com/t5/Jira-Service-Management/About-setting-up-cooperation-with-Teams-in-incident-management/qaq-p/2225744#U2227307 I've posted this response over there too.

💡Finally, in the mean time, I have an idea for you. You could leverage JSM's built-in automation feature. Simply create a manual or automatic rule that sends a dynamic message to an existing chat room. The action to use is called "Send Microsoft Teams message". You can include smart values (dynamic variables) and use markdown for formatting. I think you're probably more interested in a per-incident chat room, but it's something! Here's more about Teams and automation: https://support.atlassian.com/cloud-automation/docs/use-automation-with-microsoft-teams/

Let us know what you learn from Atlassian Support or post your bug ID so we can follow the issue!

Rachel Wright
Author, Jira Strategy Admin Workbook

[Leigh Elliott]

Thanks Rachel,  yes I've been meaning to log a support ticket for this.  I created the post above just in case the fix was simple and someone had already resolved.  I checked just before Christmas and it was still giving the error.

Not a high priority for us either, more nice to have and certainly not something I could be bothered to setup an automation rule for as a workaround (although it might be helpful for others so thanks for sharing). 

Either the new feature works out of the box Atlassian or it doesn't, ggrrrrr....

[Jason Walker]

I have raised a bug here, Create teams chat fails with Error Server Response: 422 (atlassian.com)

[青山 明]

Did this issue get resolved?

[Jason Walker]

I have the same issue too, just setup yesterday. 

It does allow me to create a meeting, if you start the meeting and then you can use the meeting for the chat comms as a workaround. 

Would be great to get to the bottom of the chat error though.