Official Microsoft Teams Jira Connector documentation guide.

Microsoft Teams Jira Connector provides one-way integration from Jira to Microsoft Teams. It is much more secure and robust integration. The optional 2-way integration with a Microsoft Teams bot is coming soon.

Marketplace link:

Use cases for Microsoft Teams Jira Connector

There are a few use cases presented below, but of course there are many more ways to use Microsoft Teams Jira Connector:

Jira feed

Setup a Jira-feed channel for your team to stay on top of Jira changes. Filter the notification down to get only important information.

Component watcher

Your team owns a set of components and you want to get notified when somebody creates an issue related to your components. You will setup the components filter with At least one should be present matching strategy.

Epic follower

You own an Epic Microsoft Teams Jira Connector Alerts and you want to know when an issue if added or commented and has this Epic.

You will setup the Custom Fields filter to narrow down notifications by the Jira Epic link.

Project owner

You own a project and want to know when an issue is transitioned to Done or commented. You can setup event filters with issue status transition filter to narrow down the amount of notifications you get. And don’t forget to select the Jira project you care about as another filter also.

QA Demo ready

Your QA teams assists your development team with quality processes and want to get notified when a particular issue gets transitioned to QA Demo Ready status, so that they can proactively schedule the demo, spread the load between the team members and prepare accordingly.

You can use issue transition filter to get notified only about the transitions you care about.

IT Support audit log

You’ve got a few IT Administrators who uses Jira Service Management to get service requests from other teams, they want to get notified about new requests in the support-feed.

They can use Microsoft Teams Jira Connector to setup a rule against they Jira Service Management project to improve their SLAs and look more professional.


There is are global and project-level configuration pages.

The project-level configuration is in the Project Settings → Microsoft Teams.

The global configuration is in the System → Microsoft Teams.

Microsoft Teams channel configuration

Go to the Microsoft Teams channel configuration and click Connectors.

microsoft teams Jira connector add connector

Find Incoming Webhook and press Add button. Put the name as Jira and download the Jira logo from the Internet.

Set the name and the icon of the Connector.

Copy the webhook URL that will be used later on during the configuration process.

Microsoft Teams Jira Connector configuration

Microsoft Teams Jira Connector has notion of rules, where each rule indicates an intent to get notified about something. You and your teams can have as many rules as you want.

In order to create a rule click the blue Create button which will trigger the creation dialog.

Each rule has 3 main sections: Rule information, rule destination and filters.

Rule information is the name of the rule to better identify it. Rule destination is the Microsoft Teams channel where notifications should be sent.

Rule filters is a set of filters which helps to narrow down the important to you notifications and ignore the ones you do not care.

You need to select All project or a concrete project you want to configure against. On the project level you cannot change the project or select All projects.

If the select project has components the two components-related filters will appear.

You also can configure whether you want to receive the issue details (facts) as part of the message. This can be done in the Message configuration section.

In order to save the rule you need to press the Save button. The cancel operation will close the dialog without saving the settings.

When the rule has been added it will appear in the main rules list.

Matching strategies

Some filters have a matching strategy will provide more flexibility on how they should be matched. Currently matching strategies are supported for labels, components and custom fields.

  • All matching strategy tells Microsoft Teams Jira Connector to make sure that all items selected/entered match the values in the issue.

  • Any matching strategy tells Microsoft Teams Jira Connector to make sure that at least 1 selected/entered is present in the corresponding field in the Jira issue.

A few example are below:

  • You want to get notified when an issue with labels crm-team-escalate and infra-changes gets Done you will be using labels filter with All matching strategy and those two labels entered.

  • You want to get notified when a ticket related to one of the components you owned gets created. You will filter events by Issue created event and add you components to the components list with Any matching strategy to make sure that you or your team gets notified when at least 1 components is used in the issue.

  • You want to get notified when an issue with Epic Link has been commented. You will use a custom field filter for Epic Link field name where the value will be the ticket id of the epic (DEV-123) and the matching strategy All.

When you just installed the App, 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.

Rule deletion

Important: after you delete the rule there is no way to restore it. Be careful.

When a person deletes a rule they have a confirmation dialog which is the last stop before the deletion process can be aborted.

Frequently Asked Questions

You can check the FAQs at Microsoft Teams Jira Connector product page.

Get help or suggest a feature

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.

Please include the following information in your support request for a bug:

  • your Jira url

  • the time when you saw the problem

  • the description of the issue.

Official Roadmap