269
Customers have installed this app in at least 269 active instances.
269
Customers have installed this app in at least 269 active instances.
    by Move Work Forwardfor Jira Cloud and Jira Server 7.0.5 - 7.5.3
    Supported
    Move Work Forward supports this app.

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    Move Work Forward supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.
    Jira Service Desk
    This app is compatible with Jira Service Desk.

    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 or custom fields.

    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 (string comparison only).
    • 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:

    Also by Move Work Forward:

    Reviews for cloud

    (7)
    Sign in to write a review
    by Scott Christian-Lim on 2017-09-08
    Whilst webhooks can do the core functionality, the implementation of this add-on does include some benefits as highlighted in other reviews such as filtering allowing me to setup several channels and get a specific notifications to each channel. The team behind the add-on are also very active, which me requesting a couple of feature requests (support of custom fields, support naming connections) both of which were implemented shortly after. Certainly worth a try.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Art Mack on 2017-04-22
    Webhooks works just fine for 0$ so I am no sure why you would use this plugin
    1 out of 2 found this review helpful
    Was this review helpful?YesNo
    Move Work Forward

    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.

    by Martin Widemann on 2017-03-20
    plugin works fine. unfortunately it's totaly senseless, because you can use JIRA webhooks for the same functionalty instead of this plugin.
    2 out of 5 found this review helpful
    Was this review helpful?YesNo
    Move Work Forward

    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.

    by Gregory Van Den Ham on 2017-02-18
    Not sure why you'd pay $600 for something you can do for free by going into the Jira control panel - system settings and creating webhooks like microsoft teams suggests.
    2 out of 3 found this review helpful
    Was this review helpful?YesNo
    Move Work Forward

    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.

    by Leo on 2017-02-11
    Does the job. We configured it to send notifications on a particular state of an issue, plus a few escalation rules for high priority bugs.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo

    Reviews for server

    (7)
    Sign in to write a review
    by Scott Christian-Lim on 2017-09-08
    Whilst webhooks can do the core functionality, the implementation of this add-on does include some benefits as highlighted in other reviews such as filtering allowing me to setup several channels and get a specific notifications to each channel. The team behind the add-on are also very active, which me requesting a couple of feature requests (support of custom fields, support naming connections) both of which were implemented shortly after. Certainly worth a try.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Art Mack on 2017-04-22
    Webhooks works just fine for 0$ so I am no sure why you would use this plugin
    1 out of 2 found this review helpful
    Was this review helpful?YesNo
    Move Work Forward

    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.

    by Martin Widemann on 2017-03-20
    plugin works fine. unfortunately it's totaly senseless, because you can use JIRA webhooks for the same functionalty instead of this plugin.
    2 out of 5 found this review helpful
    Was this review helpful?YesNo
    Move Work Forward

    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.

    by Gregory Van Den Ham on 2017-02-18
    Not sure why you'd pay $600 for something you can do for free by going into the Jira control panel - system settings and creating webhooks like microsoft teams suggests.
    2 out of 3 found this review helpful
    Was this review helpful?YesNo
    Move Work Forward

    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.

    by Leo on 2017-02-11
    Does the job. We configured it to send notifications on a particular state of an issue, plus a few escalation rules for high priority bugs.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo

    Pricing

    Pricing details are loading…

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does cloud app pricing work?

    Cloud pricing is subscription based. 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 host products and 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 host 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 products and apps is as follows:

    • Monthly subscriptions with up to 10 host 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 per-user pricing is not yet available for this app, please contact the vendor for further information.

    If you've opted for annual billing for your host 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?

    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.

    Paid-via-Atlassian pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 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 host 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 host product. For Jira Server 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 (50 users) and Jira Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of Jira Server 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.

    Do you offer academic, community, or open-source licenses?

    For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    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 host 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.

    Learn more

    Move Work Forward provides support for this app.

    Move Work Forward provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    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.1.5 Jira Server 7.0.5 - 7.5.3 Released 2017-11-21

    Summary

    Little bug fix related to components filters

    Details

    • Little bug fix related to components filters

    Installation

    1. Log into your Jira instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Microsoft Teams Jira Connector via search. The appropriate app version appears in the search results.
    5. 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.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. 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.

    1. Log into your Jira instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Find new add-ons screen loads.
    3. Locate Microsoft Teams Jira Connector.
    4. Click Free trial to download and install your app.
    5. You're all set! Click Close in the Installed and ready to go dialog.

    Similar apps