Hello Atlassians,
my company is using Microsoft Teams lately and there is a request to integrate it with Jira. The problem is that i am receiving this 400 Client error. And its getting annoying!
I have noticed that after the creation of the webhook as the documentation and tutorial of microsoft teams says , when i create or delete an issue i am not receiving a notification in Teams. However when i update or comment or whatever i do!
Before anyone say if i have checked the checkboxes relating to the events inside the hook , Yes i did it.
Any ideas ? I have read a lot of issues/related issues but nothing seems to help...
Thanks in advance
CM
Hi,
So, after being in contact with the app vendor support they yesterday made a new deployment on production. I have verified that it now works on my selected events (Created, Updated, Commented). No changes had to be done on my side.
Regarding the warning in the log files, I think it might be Jira-related since you get those even if you create a webhook to post to a test site. I changed the log level to ERROR on this class:
c.a.webhooks.plugin.PublishTaskFactoryImpl
After all, they are just warnings :-)
Finally, I noticed that they pick up statusCategory name rather than status name. Might be another deployment soon.
Best regards
//Mattias
I confirm the same results :)
Thank you @Mattias Kallvi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my case it's as follows:
In all of the cases above I get a warning in my Jira log file just like the ones Willems descibes.
I have e-mailed the addon vendor. If I get any response I will let you know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello we are seeing the same. We do not see anything popup with the jira server connection in ms teams and the webhook.
The log shows the following with us (i edited out the webhook url)
2019-02-19 12:22:38,546 httpclient-callbacks:thread-1829 WARN anonymous [c.a.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Client error - 400 when posting to web hook at 'https://connectors.msteams-atlassian.com/JiraServer/....'
2019-02-19 12:22:55,513 httpclient-callbacks:thread-1829 WARN anonymous [c.a.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Client error - 400 when posting to web hook at 'https://connectors.msteams-atlassian.com/JiraServer/...'
so it does seem to trigger something when creating issues but it fails
Edit: updating, placing comments etc also works with us but deletion and creation of issues does not come through in ms teams using the webhook and fail with 400 bad request error
we are using Atlassian JIRA Project Management Software (v7.7.0#77001-sha1:3be3151)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Teams gave me a webhook uri starting with "https://outlook.office.com...." - inspired by your comment i replaced that by "https://connectors.msteams-atlassian.com/....".
Then it started started to work....strange....
There should be a "Test" Button which helps to verify the proper function of webhooks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This option does not work for me on JIRA DC on-prem v8.13
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems to start displaying created issues messages with us today, not sure if something was changed on https://connectors.msteams-atlassian.com to fix the issue or if it's only temporary or a fluke but we had 2 created issues messages displayed in ms teams
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello again,
the only way that i found to make it "theoretically" correctly work is like, adding a post function transaction in the workflow action between "Create" & the first status with the webhook.
I could say that this this is just a workaround solution!
Best regards
CM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.