Customers have installed this add-on in at least 464 active instances.
    by jSoftware Pte LtdAtlassian Verified
    jSoftware Pte Ltd is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Server 6.3.15 - 7.3.1
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.
    jSoftware Pte Ltd supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.
    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.

    Slack , Slack JIRA Server, Slack Connector

    Slack , Slack JIRA Server, Slack Connector

    Support your client by Slack team

    Multiple Slack Teams and Message builder

    Your own Slack setting

    Discuss with your team and review them by Slack tab

    Support client directly via Slack App

    Multiple Slack teams in a JIRA project

    Custom Slack message notification

    JQL support

    Multiple events

    JQL filter setting

    New version release notification

    Custom bot name and icon bot

    Whitelist Slack teams

    Summary list of Slack project

    More details

    Setup instruction


    Report issue or feedbacks https://jsoftconnector.atlassian.net/servicedesk/customer/portal/1

    User reviews

    Sign in to write a review »
    by Tom Jackson on 2017-01-23
    We are doing an evaluation of this plugin and it mostly works as advertised. We are however having issues with two key features (and that could be very handy to have). The docs describe that @mentions on a Jira issue should result in a direct message to the mentioned user from the slackbot user. We cannot get this to work. The docs also describe that updates on watched issues should result in a direct message to the watchers from the slackbot users. We also cannot get this work. The docs also describe that assigned issues should result in a direct message to the assignee from the slackbot users. This DOES work for us. We have been working with the vendor's support for a few weeks but haven't achieved a resolution, with on again, off again responsiveness. I will gladly increase my rating if/when I see direct messaging fully operational.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Mattias Sandström on 2016-12-30
    Don't bother with this add-on. It is too unreliable and has too many configuration glitches. Instead, use a WebHook and the App on the Slack side.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    jSoftware Pte Ltd

    Hi Mattias,

    First off , thanks for your feedbacks . Actually we were thinking about WebHook integration but It quite un-control with webhook integration. We want to get more benefit from Slack api through rest api and custom app. for example , you able connect multiple Slack team in JIRA "just one click" . So please help take 3 mins to revise our document guide in Confluence https://jsoftconnector.atlassian.net/wiki/display/JS/Slack+connector+for+JIRA+server .

    Other things , If you are project admin , you need to worry about webhook or anything . you just go to project Admin and click "Connect" , then Slack connector will do the rest for you.

    Hope above explanation that make sense.

    Best regards,


    by feniljanakkumarpatel on 2016-10-13
    it works perfectly. Looking forward to buy licence. keep it up guys.
    Was this review helpful?YesNo
    by Kumaran on 2016-09-30
    Excellent customer service in answering questions posted. Integration works as promised. Great tool to promote collaboration between teams and increase productivity. Developers are quick in fixing bugs and releasing new features requested. Overall, great tool & effort !
    Was this review helpful?YesNo
    by Warren Goldman on 2016-09-01
    get nothing but the spinny wheel when I click on the slack tab... tried clicking configure, wants a client id (issued when you created your app (required). - I DON'T REMEMBER CREATING AN APP - NOT SURE WHAT THIS IS REFERRING TO SAVE FOR CLIENT SECRET WOULD BE NICE IF IT WORKED, IS MY GUESS../
    1 out of 2 found this review helpful
    Was this review helpful?YesNo


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons 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 add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on 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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications 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 add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Note: While this add-on has features specific to JIRA Service Desk, the add-on 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 add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

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

    Can I extend my free trial?

    For server add-ons, you can extend your add-on 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 add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons 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 add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more


    jSoftware Pte Ltd is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    jSoftware Pte Ltd supports Slack Connector for JIRA Server. You can visit the support site to get help.

    Get support


    Version 2.6.4 JIRA Server 6.3.15 - 7.3.1 Released 2017-02-17


    Update direct messages and bugfixing


    • Do not send my changes option
    • Bugfixing


    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 Slack Connector for JIRA Server via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Slack Connector for JIRA Server. You're prompted to log into MyAtlassian. Slack Connector for JIRA Server 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 Slack Connector for JIRA Server versions compatible with your instance, you can look through our version history page.

    Similar add-ons