Help Troubleshooting Webhooks to MS Teams?

[Development Admin]

I'm trying to get Jira Server to fire a webhook to MS Teams whenever a version is marked released.  I went through the setup and selected the Version: released event, and grabbed my webhook url from MS Teams.  When I go to test it and release a version, nothing shows up in Teams and all I get in the Jira logs are a "Client error - 400 when posting to web hook" warning.  I tried adding different events and just get more of the same.  I am not specifying any JQL (though have tried it with some), exclude body is not turned on, and I have no linked transitions.

The other posts I've found of other people with a similar problem, it just seems to start working again.  Any ideas what I can check next?

[Helpdesk Helpdesk]

Tim,

We setup JIRA with AD from the start

We have trainers that need access to JIRA while in the field and don't have a VPN setup yet.  We don't want to be vulnerable to a hack using AD over the web.

[Tim Eddelbüttel]

If you really want to do this, make sure that you have in booth user directories the same usernames!

Did you switched before from internal to AD or started you with AD? Your groups are managed in JIRA or AD?

1. Export your existing users from cwd_user in a CSV file (username, first name, last name,  mail)
2. Export your existing memberships (https://confluence.atlassian.com/x/qwc_EQ)
3. Check that you have a working admin user in your internal directory

If your not familar how to export these data, take a look at the Crowd Docs (https://confluence.atlassian.com/x/UIdcGg) and change the MySQL query to your needs. It's nearly the same.

Download the JIRA CLI (https://bobswift.atlassian.net/wiki/display/ACLI/Downloads) and play with your exported data on a testing environment.

Just out of interest, could you explain what you mean with security reason on your AD?

[Rodrigo Rosa]

Hello!

You may use this https://confluence.atlassian.com/display/JIRA/Migrating+Users+between+User+Directories document as reference to migrate all users to JIRA internal.

Regards,

Rodrigo Rosa