270
Customers have installed this add-on in at least 270 active instances.
    by ServiceRocketAtlassian Verified
    ServiceRocket is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Cloud
    Supported
    ServiceRocket supports this add-on.

    Get support

    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Power up your Salesforce CRM business workflow through seamless integration with JIRA Cloud

    Power up your Salesforce CRM business workflow through seamless integration with JIRA Cloud

    Connect Salesforce & JIRA Cloud in Custom Ways

    Find Salesforce information from within JIRA

    Get Started Quickly

    Bring Salesforce to a bigger audience in JIRA Cloud. Associate JIRA issues with Salesforce Cases, Accounts, Opportunities, and more. Push and pull Salesforce information from JIRA.

    Let JIRA Cloud users to find the Salesforce information they are looking for. Create JIRA issue or associate to an existing JIRA issue right from the search results.

    Connect the best of both worlds together in just a few steps. Authorizing connection is a breeze. Import settings from Salesforce first, configure later.

    More details

    *** Want to see live demo? Join our Jam sessions! ***

    Your development and product management teams live in JIRA. Your support and sales teams close in Salesforce. They all deal with product issues and need an integrated view of what's going in order to be effective. The connector links, pushes and pulls Salesforce information from JIRA for an integrated experience from either interface.

    • Connect JIRA Cloud to multiple Salesforce instances.
    • Choose which Salesforce objects and fields are available in JIRA Cloud.
    • Search for Salesforce objects from within JIRA Cloud.
    • Create Salesforce object from JIRA.
    • Associate Salesforce objects to JIRA issues, push and pull changes to/from Salesforce.
    • See aggregated view of comments from associated Salesforce Cases.
    • View, create and associate JIRA issue in Salesforce. Install the Salesforce App certified by Salesforce.
    • ...and more!

    Want help getting the Connector setup and configured in your environment? Check Out Our Implementation Services.

    User reviews

    (15)
    Sign in to write a review »
    by Kyle Farris on 2016-11-28
    This new add-on is really inferior in every way to their previous add-on for how we are using it. Our primary issues are as such: - There is no way of associating a link to any kind of context. For example, we link a custom SF object, Release__c, which contains our product release codes, to our JIRA issues in different ways: "Release Affected" (release user reported issue in), "Release to Be Fixed In" (the release it will be fixed in), and "Additional Releases Affected" (other releases this issue affects). There is NO WAY to associate these contexts to the linked releases... just blind linking of releases. I feel like it would be simple enough to add an additional field for us to type or select a "label" or "tag" to the link... - We have no way of knowing when new links are created in the issue. We have a report that we created using the JIRA REST API that shows the 100 most-recently-updated issues. Well, when any kind of link is created using the add-on, the "updated" field on the issue isn't modified in any way. So, all changes related to SF links are never found and our report is now useless. Both of those previous items were never an issue in the previous add-on because they worked via issue fields and no issue properties. We've brought up these issues with Service Rocket and have either gotten a "We'll see if it's feasible" or have just gotten completely ignored. We're paying $500 a month for this POS service and have been treated like we don't matter at all.
    Was this review helpful?YesNo
    by Michelle Melancon on 2016-11-04
    Awful. The documentation that Service Rocket keeps directing me to in order to work through the endless issues we are having has absolutely nothing in it and we are forced to wait a day or two for replies on urgent issues. Completely change the current behavior, force an upgrade, provide no documentation or support. Awesome.
    Was this review helpful?YesNo
    by Anoop Chatterjee on 2016-10-20
    this addon exposes all salesforce objects to your jira users. huge violation - need to find how to lock this down. jira users should not be able to see opportunities, amounts etc.
    Was this review helpful?YesNo

    ServiceRocket

    Anoop, in the Connection Configuration you can add/remove objects and fields as you need. This will control what is displayed and searchable in JIRA. I hope this helps, otherwise let us know at support@servicerocket.com.

    by Chase Whitener on 2016-10-19
    You forced a migration on us. Your newer product removed nearly every single feature we were using and you refused to help us or even acknowledge the fact. You've left my team and me in an extremely bad place right now. Terrible practices on top of a really poorly done redo of your older add-on.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    by Zack Foster on 2016-10-17
    Good experience so far. Set up is pretty straight forward. Found one issue with SF displaying all projects from JIRA (rather than just those that were linked to SF), but ServiceRocket team was responsive and got it fixed. A couple things we would like to see. -Linking by JIRA ID (right now only Summary can be used; when the ID is known, it is much faster) -Sending attachments from SF to JIRA - Our workflow has support issues traveling from SF to JIRA, so it makes much more sense for us to be sending attachments to JIRA, rather than from JIRA to SF. Only the latter is supported now. We're still in our initial adoption phase, so I will update with any new issues/mods that pop up. On a side note, we have a lot more JIRA users than SF (like 10:1 ratio). Since the monthlies are based on the JIRA user count rather than SF, the price is a bit high, but not prohibitively so. Update [10/17/2016]: 1) Linking by JIRA ID works now, thanks ServiceRocket 2) On sending attachments, the request is that they sync _automatically_. Right now, it still requires a manual push command for sending from SF to JIRA. Very responsive on the first item, thanks guys.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    ServiceRocket

    Hi Zack, thanks for the feedback! In regards to your suggestions above:

    • I presume you want to associate a Salesforce object with an existing JIRA issue (in Salesforce). If so, you should be able to search either via issue key (e.g. DEV-102) or summary of the JIRA issue. (see docs).
    • Attachments can be sent from/to both ways - if you attach a file to Salesforce object, you can send it to JIRA by clicking on the 'Push' button. That is, if you have the 'Synchronize attachments' setting turned on in JIRA, and the association is non-read-only. See docs.

    As always, if you need further assistance, contact us at support@servicerocket.com.

    - Azwandi, product manager.

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does cloud add-on 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, your pricing tier for host products and add-ons is automatically adjusted (as necessary) based on the number of users in your instance.

    If you've opted for annual billing for your host product, add-ons are also billed annually. Annual subscriptions for this add-on include a discount (12 months for the price of 10).

    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 cloud pricing tier?

    The cloud add-on tier is set automatically based on the maximum tier of the licensed JIRA applications on your instance. For example, if you have JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, your add-on tier is 50 users.

    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 cloud add-ons, you cannot extend your free evaluation period. All cloud add-ons 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 add-on.

    Support

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

    ServiceRocket supports Salesforce & JIRA Cloud Connector. You can visit the support site to get help.

    Get support

    Versions

    JIRA Cloud Released 2016-12-02

    Summary

    Minor version update

    Details

    Minor version update

    Installation

    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 Salesforce & JIRA Cloud Connector.
    4. Click Free trial to download and install your add-on.
    5. You're all set! Click Close in the Installed and ready to go dialog.

    Similar add-ons