Microsoft Teams Jira Connector provides one-way integration from Jira to Microsoft Teams. It is a much more secure and robust integration.
Note: two-way integration is in development and should be released around Q1 2021.
Frequently Asked Questions
You can check the FAQs at Microsoft Teams Jira Connector product page.
You can find alerts configuration on Alerts Configuration page.
Scheduled reports configuration
You can scheduled reports configuration on this page.
There is a global and project-level configuration. The global configuration available to the global administrators only.
The global configuration is in the System → Mail → Microsoft Teams.
The project-level configuration accessible in the project settings Project Settings → Microsoft Teams. Only project or global administrators can change the project-level configuration.
Go to the Microsoft Teams channel configuration and add a connector.
Find Incoming Webhook and add one. Put the name as Jira and set the Jira logo.
Set the name and the icon of the Connector.
Copy the webhook URL that will be used later on during the configuration process.
Navigate to the configuration page, select the projects you want to get notification about and paste the webhook URL (or select a managed url).
Setup the filters. Do remember that some values are only available when there is only 1 project selected.
You can configure custom fields filters. For instance, below you can see the Epic Link filter.
The configuration gets stored when you press Save button.
You can have multiple notification rules.
When you just installed the plugin, please try to create a very simple configuration to the event "Someone leaves a comment" and with no filters. This will validate that the plugin has the correct license and your Jira can access Microsoft Teams.
Microsoft Teams message fields configuration
When you create a rule you can configure which issue fields are sent to Microsoft Teams. This is done using the section Microsoft Teams message fields at the bottom of the rule creation dialog.
In the Global configuration you can configure the projects that cannot use this App.
Admin events notifications
Global administrators can configure Microsoft Teams Jira Connector to receive system level event notifications. It includes events related to users, plugins and re-index all completed event.
Custom event type mapping
In the Global configuration you can map custom user event type to the system ones in order to process them as well.
Important: without this mapping custom event types are not handled, as the App does not know how to handle those. By mapping them to a system event you can help them App to understand them.
Destination Url Management
With Url Management you can configure named Microsoft Teams Incoming Webhook urls and optionally restrict them to particular Jira projects. Managed urls provide a few benefits:
You can identify urls by name, which provide much more flexibility to administer
Restrictions by Jira project permit enables your project admins to use them without asking for a new url. For instance, you can create a url for Customer Success teams and permit to use it only by Customer Success Jira project. The configuration becomes much simpler.
Simplified url creation.
Important: The urls do not work as filters. If you configured to which project url is available but you use it globally, the notifications will be sent according to the rule.
The Url Management is available ONLY to global administrators.
You can create a new Managed Destination Url by clicking
You can click Test to verify the delivery/reachability of the Microsoft Teams channel.
When the url is created it is visible in the Urls table.
In order to use the newly created Managed Destination Url you need to create a new rule or edit an existing one. In the Destination section you can opt in to use the Managed url.
Afterwards you or the user of the url can select a url from available urls.
The rule with a Managed Destination Url looks like this.
And the message for a newly created Jira Service Management support request looks like this.
Additional configuration via environment variables
moveworkforward.pool.size - this variable can be used to control the amount of thread in the thread pool (from version 3.10.08).
Please make sure that you have the latest App version, we fix the issue pretty quickly and there is a chance that your problem had been fixed.
If you see some problems with the App we recommend to check the browser console for errors as well as enable debug mode for the App's namespace to see any errors.
App namespace to enable DEBUG log level: com.moveworkforward
Here is official Atlassian’s documentation on how to enable the debug mode - https://confluence.atlassian.com/jirakb/change-logging-levels-in-jira-server-629178605.html
Download the support zip
You can send us the support zip which contains the log files. You can download it following this official Atlassian documentation.
You can create a Jira Service Desk support request with all information you could gather, please include the screenshot of the configuration (please don't worry about the webhook URLs, we won't store or use them) and the logs or errors you could find in the browser or on the server-side.