Watch 2-minute demo on how to integrate Microsoft Teams and Jira
Either you have Jira Server (including Data Center) or Jira Cloud (including Jira Service Management and Core), you are covered. Stay on top of important things that happen in Jira and omit not important stuff.
Whatever you do in Jira you and your team can get notified in a particular channel in Microsoft Teams. You can filter notifications to reduce the noise and stay on top of the things you want to know first. Use multiple Jira filters, including Jql and saved Jira filters.
Use Microsoft Teams Bot to search, embed, create and move work forward. Some videos here - https://www.youtube.com/playlist?list=PLSsd6IAGxHntpM8UmthSzJrWQw0a2yFjt
Join the 5000+ happy customers. It’s free to start!
Try it FreeMove Work Forward is an independent Atlassian Marketplace Vendor. We do not have any affiliation with Atlassian.
Move Work Forward does not collect any data and we do not know how you use our products or what data is stored, so we rely on your feedback.
Yes, we support all types of Jira installations.
Yes, you can schedule the video call here.
Yes, we do, and the Microsoft Teams Jira Connector public roadmap is here. Please contact us if you or your team have any proposals.
Move Work Forward provides a fully functional of Microsoft Teams Jira Connector for 30 days.
Once the trial period is over, the cost of the app will automatically be included in your next bill unless manually deactivated via the Manage Apps page under the Jira Administration menu. Evaluation licenses can be extended.
You can generate an evaluation license here, or by logging into your my.atlassian.com account and searching for Microsoft Teams Jira Connector by Move Work Forward.
Cloud: You can find the cost to purchase Microsoft Teams Jira Connector on your Jira Cloud instance here.
Microsoft Teams Jira Connector for Cloud is sold as a monthly or annual subscription. You are eligible for support and automatic version updates as long as your subscription is active.
Data Center and Server: You can find the cost to purchase Microsoft Teams Jira Connector on your Jira Server instance here or your Jira Data Center here. Microsoft Teams Jira Connector for Server or Data Center 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 here.
You can use Microsoft Teams Jira Connector by Move Work Forward in two ways:
Yes, it is here.
You can use Microsoft Teams Jira Connector by Move Work Forward in two ways:
Yes, it does.
To revoke the access, you need to uninstall the Microsoft Teams companion App and in the global settings, execute a disconnect action.
Microsoft Teams Jira Connector does not receive or store your credentials.
If you use uni-directional (incoming webhooks) integration Microsoft Teams Jira Connector for Jira Server or Data Center, Microsoft Teams Jira Connector does not store anything outside of your Jira instance(s).
Otherwise, Microsoft Teams Jira Connector stores the following information:
Microsoft Teams Jira Connector persists this information to act-on-behalf of Microsoft Teams user.
Definitely yes, you can use Microsoft Teams Jira Connector without being the Jira administrator. However, you may need some help from your Jira administrator to configure the application in some circumstances.
When the team members reside in a Microsoft Teams channel, they can view all data posted in there.
When you have problems with Microsoft Teams Jira Connector not sending messages to Microsoft Teams you can try the following:
If after those steps you do not receive a notification in Microsoft Teams, it is possible that your Jira server(s) cannot reach the Internet and Microsoft servers. The easiest way to test this is to open the terminal on your Jira server and try to post a test message directly to Microsoft Teams https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-using#setting-up-a-custom-incoming-webhook
As a next step, we advise to follow up our documentation related to the troubleshooting and contact us with the log file.
We usually reply within two business day, so please make sure our email has not hit your spam filters. If you haven't seen a reply within 48 hours or it is super urgent - please contact us at support at move work forward dot com.
You need to make sure your Microsoft Teams administrator permits to use 3-rd party applications.
It depends on your permissions in Jira. When you have sufficient privileges, you can access the following pages:
We are humans who have families and hobbies, on top of this, we inspired to provide the best integration between Microsoft Teams and Jira, which requires time and effort to execute well. Notwithstanding these arguments, we strive to provide excellent customer support.
Yes.
You need to export your data from one Jira and import it in another, that's a joke. Migration is not so simple to do at the moment. We are working on automated migration, but it is not there yet. Please reach out if you need help.
Please use our Jira Service Portal (called F1) to submit a support request, feature request or just an enquiry. Do not forget to describe your problem in great details and attach the debug log if possible. We cannot guess about your issues.
At this stage, only Jira Server and Jira Data Center customers can extend their evaluation licenses. You can do this by completing this form and updating your product license under the "Manage Add-ons" page in the Admin panel.
Yes, and we have enrolled in Bug Crowd Bounty program.
Please contact us to discuss your requirements.
When purchasing an app license, the user tier must match that of Atlassian Jira. This is a requirement of the Atlassian Marketplace, as detailed in this Atlassian FAQ. Atlassian handles all licensing for Marketplace vendors so we can focus on what is important to us - providing quality software and supporting our customers. As a result, we are unable to modify the licensing to be restricted to specific user groups within a Jira instance.
All licensing matters are handled directly through Atlassian, so, unfortunately, there is nothing we can do as vendors to rectify this. Please reach out to sales@atlassian.com and open a ticket directly with Atlassian, they will be able to resolve this for you.
The Jira Id imprinted on the Global Configuration page in the System settings. Jira Id used to map Microsoft Teams and Jira tenants.
You can follow the the troubleshooting process defined in Microsoft Teams Jira Connector user guide.
We store data in our secure environment in AWS in the USA. If you have issues with this, please reach out. We are in progress to add additional regions: Frankfurt and Sydney.
Atlassian allows customers to trial apps from the Marketplace for a total of 6 months before they require customers to purchase a commercial license.
Receiving this message means that you have reached that maximum amount of free trials for Microsoft Teams Jira Connector, and are no longer eligible to use for the product for free. To continue using Microsoft Teams Jira Connector, you must purchase a commercial license here.
A 503 error is usually caused by Jira itself being temporarily down.
There are typically two causes of a 503 error: