Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

About setting up cooperation with Teams in incident management of JSM

青山 明 December 27, 2022

We have set up integration with Teams in the incident management of jira service management.
I have now created an incident issue and completed the connection with teams in the "Microsoft Teams" item in the details on the right side of the issue. Then, I am setting the chat, but the following error message is displayed on the setting screen.
"Error server response 422"
What does this mean and what should I do about it?

1 answer

0 votes
Rachel Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 29, 2022

Hi @青山 明 ,

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: 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: I'll go post 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:

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

青山 明 January 10, 2023

This problem self-resolved. The cause of the server error is a setting problem on the Teams side. It was necessary to register two members other than myself to the team in advance.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events