Advanced Microsoft Teams Jira Connector for Jira Cloud
The documentation for Advanced Microsoft Teams Jira Connector for Jira Cloud
This documentation won't be maintained anymore.
Please visit our up-to-date documentation to be in the loop on the latest improvements and features.
How to guides
Advanced Microsoft Teams Jira Connector for Jira Cloud Guides
Rule setup
Rule filters are a set of filters that helps to narrow down the importance of your notifications and ignore the ones you do not care.
You need to select All projects 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.
Official Microsoft Teams Jira Connector documentation guide that helps integrate Microsoft Teams and Jira Cloud.
Microsoft Teams Jira Connector provides one-way and two-way integrations between Jira to Microsoft Teams.
Marketplace link: https://marketplace.atlassian.com/apps/1216325/microsoft-teams-jira-connector?hosting=cloud&tab=overview
Use cases for Advanced Microsoft Teams Jira Connector
There are a few use cases presented below, but here 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 set up the components filter with At least one should be the present matching strategy.
Epic follower
You own an Epic Microsoft Teams Jira Connector Alerts and you want to know when an issue is added or commented on 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 set up event filters with an issue status transition filter to narrow down the number 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 assist 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 the 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 use 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 set up a rule against the Jira Service Management project to improve their SLAs and look more professional.
Configuration
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.
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.
Advanced Microsoft Teams Jira Connector configuration
Microsoft Teams Jira Connector has the 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 dialogue.
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.
Notification destination configuration
We recommend using the companion Microsoft Teams application - Move Work Forward with Jira. Before you can use it in Jira - your Microsoft Teams administrator needs to install it in the necessary Microsoft Teams teams.
When you use the login functionality from Microsoft you need to make sure the pop up windows are allowed in your browser.
In order to receive notifications you need:
Login to your Microsoft account in order to read the teams and channels where the Microsoft Teams companion application is installed.
Select a Microsoft Teams team, which will trigger a load of the Microsoft Teams channels of that team.
Select a Microsoft Teams channel where you want to receive your notifications.
The teams is not visible if the companion application Move Work Forward with Jira is not installed in the team.
Microsoft Teams does not support bots/apps in the private channels, as a result, the channels are not usable.
In order to save the rule, you need to press the Save button. The cancel operation will close the dialogue without saving the settings.
When the rule has been added it will appear in the list of the main rules.
Matching strategies
Some filters have a matching strategy that 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 examples are below:
You want to get notified when an issue with labels
crm-team-escalateandinfra-changesgetsDoneyou 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 createdthe event and add your components to the components list with Any matching strategy to make sure that you or your team gets notified when at least 1 component 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 for the event "Someone leaves a comment" 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 dialogue which is the last stop before the deletion process can be aborted.
Frequently Asked Questions
You can check the FAQs on the 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
Updated: