Get notifications about Jira events into multiple Microsoft Teams channels. Start FREE today
Get notifications about Jira events into multiple Microsoft Teams channels. Start FREE today
Get notifications about Jira events into multiple Microsoft Teams channels. Start FREE today
Don't miss anything
Easy configuration with multiple filters
Support of Web, Mobile and Desktop clients
The Microsoft Teams Jira Connector sends notifications about your Team's Jira activities directly into you Microsoft Teams channels. Notifications contain necessary information to act on them.
Channel specific configuration, so specific channel receives specific events. Extended filters for a project, issue type, issue status, issue priority, issue components and custom fields.
Get notified no matter which device you use with any granularity you want. If you want to watch only an Epic linked issues, yes, you can.
Don't miss anything from Jira
Easy and granular configuration
Support of Web, Mobile and Desktop clients
The Microsoft Teams Jira Connector sends notifications about activity related to your team, projects or issues. Setup precise notifications and filters and do not miss anything important.
Project specific or global configuration. You can filter by project, issue type, issue priority, issue components, issue workflow status, project component, custom fields, assignee or creator.
Get notified no matter which device you use. Works for Jira Server, Jira Service Desk and Jira Data Center.
More details
What is supported in Microsoft Teams Jira Connector?
- Near real-time notifications about activities in Jira Server and Jira Cloud.
- Granural global and project-specific channel configuration, so different channels can receive different information.
- You can filter notifications by project, issue type, issue priority and issue workflow status.
- We support Jira Cloud (including Software and Service Desk) and Jira Server (including Data Center).
- You can read the setup documentation about Microsoft Teams Jira Server Connector
- Microsoft Teams is not open for everybody yet, so the configuration is not 1 click, but 3.
- If you have any questions or feature requests please reach out to us.
- There is also Microsoft Teams Confluence Connector available for Confluence Server
More details
What is supported by the Microsoft Teams Jira Connector?
- Receive near real-time notifications of both Jira Server and Jira Cloud activities.
-
Configure your notifications globally or by project-specific channels.
- Filter notifications by project, issue type, issue priority, issue workflow status, project components or custom fields.
- Customise notification content, assignee and creator filters (Server only for now).
- Support for Jira Cloud (including Software and Service Desk) and Jira Server (including Data Center).
- Access to our responsive customer support
- Active development of new features (please reach out if you have a request).
Note: If you don't need filtering of notifications, please setup webhooks to integrate Microsoft Teams and Jira Cloud in MS Teams.
Setup details:
- Documentation available on how to implement the Microsoft Teams Jira Server Connector
Also by Move Work Forward:
- Microsoft Teams Confluence Connector available for Confluence Server
Reviews for cloud
(11)Sign in to write a review
Hi,
Thanks Art for writing.
Webhooks don't have many filters to target notifications. For example, you can filter by issue priority, component or any custom field etc.
We can always improve things much faster comparably to the Microsoft's webhooks.
Thank you for the review, Martin.
Why did you put 1 star? The product does what is described (you confirmed this) and you can setup everything easier (via global or project configuration).
On top of this, we implemented filtering by project, issue priority, issue status and issue type, which is not supported with webhook integration.
Thanks again Martin.
Hello Gregory,
Thank you for the feedback. I do agree with you if your case is pretty simple and you are in a small organization.
You are right also if you don't need to filter by issue priority, issue type, issue status or projects. For example, if you would like to get notified in Microsoft Teams QA channel/room about issues that got into "Ready for QA" status only OR track changes in High/Highest priority Stories/Bugs in a particular Microsoft Teams channel/room, you won't be able to setup these with web hooks alone.
Thank you for your feedback again. If we can improve our product further please do let us know.
Reviews for server
(11)Sign in to write a review
Hello Gregory,
Thank you for your kind review and desire to help others. We appreciate it as we also want to help others.
We did specify in the description that for simple cases we recommend using webhooks because of the reasons you provided.
For more complicated advances notifications our App will do the job better because it allows:
- have more granular filters;
- customize the cards in Microsoft Teams (to some extent);
- have multiple configurations and have better team visibility on the notifications setup.
If you are missing any features, filters or see how we can improve our Apps further please feel free to reach out.
We are listening to your feedback.
Thank you for the feedback.
We are working on a bi-directional integration as part of getally.com
Hi,
Thanks Art for writing.
Webhooks don't have many filters to target notifications. For example, you can filter by issue priority, component or any custom field etc.
We can always improve things much faster comparably to the Microsoft's webhooks.
Reviews for Data Center
(11)Sign in to write a reviewHi,
Thanks Art for writing.
Webhooks don't have many filters to target notifications. For example, you can filter by issue priority, component or any custom field etc.
We can always improve things much faster comparably to the Microsoft's webhooks.
Thank you for the review, Martin.
Why did you put 1 star? The product does what is described (you confirmed this) and you can setup everything easier (via global or project configuration).
On top of this, we implemented filtering by project, issue priority, issue status and issue type, which is not supported with webhook integration.
Thanks again Martin.
Hello Gregory,
Thank you for the feedback. I do agree with you if your case is pretty simple and you are in a small organization.
You are right also if you don't need to filter by issue priority, issue type, issue status or projects. For example, if you would like to get notified in Microsoft Teams QA channel/room about issues that got into "Ready for QA" status only OR track changes in High/Highest priority Stories/Bugs in a particular Microsoft Teams channel/room, you won't be able to setup these with web hooks alone.
Thank you for your feedback again. If we can improve our product further please do let us know.
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$29 | 25 users$49 | 50 users$89 | 100 users$149 | 250 users$199 | 500 & upAdditional pricing details |
Pricing FAQ
- How does cloud app pricing work?
Cloud apps are sold as a monthly or annual subscription. You are eligible for support and automatic version updates as long as your subscription is active.
When your subscription renews each month, you are automatically billed for apps based on the number of users in your instance.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my cloud pricing?
Apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you pay the 50-user price for apps.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for licensing across maximum users still apply.
The pricing structure for cloud apps is as follows:
- Monthly subscriptions with up to 10 Atlassian product users are billed at a flat rate price.
- Monthly subscriptions with more than 10 users are billed per user, starting at the first user.
- Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.
If you've opted for annual billing for your Atlassian product, apps are also billed annually at a discount (12 months for the price of 10).
- Do you offer academic, community, or open-source licenses for cloud apps?
Academic, community and open source licenses are not available for cloud apps.
- Can I extend my free trial?
For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
This app does not have a a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.
However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app does not have a Data Center approved version, you should purchase a Server license if you decide to install this app in a Data Center product.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Move Work Forward is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Move Work Forward is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Jira Cloud • Released 2017-08-27
Summary
Components and custom fields filters were added
Details
Now you can filter not only by project and issue related filters, but also:
- Specific issue component.
- Value of a custom field (Compared as a string). For example, if you would like to filter by Epic Link, you can select "Epic Link" as a custom field and "DEV-50" as a value (where DEV-50 is the issue key of the Epic).
As always, you are very welcome to propose how to improve our product further for you via our Custom Success portal.
Versions
Version 1.11.3 • Jira Server 7.0.5 - 7.12.3 • Released 2018-11-03
Summary
Improvements
Details
- Better error handling
- Logging for throttling
- Webhook URL is checked to start with a specific string.
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Microsoft Teams Jira Connector via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Microsoft Teams Jira Connector. You're prompted to log into MyAtlassian. Microsoft Teams Jira Connector begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Microsoft Teams Jira Connector versions compatible with your instance, you can look through our version history page.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Find new apps or Find new add-ons screen loads.
- Locate Microsoft Teams Jira Connector.
- Click Free trial to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
Similar apps
