Connector for Salesforce and Jira (Cloud) by Appfire

Gets half the job done

Requires you to write and deploy triggers in order to listen for changes to Salesforce records...in this day and age it feels like this should be standard feature for it to be able to deploy triggers on selected objects....the DLRS rollup tool has been building and deploying triggers on admin's behalf for a decade. Also this integration is sub-par to ServiceRocket's original integration with JIRA Server. You have to map ('bind') fields for every single issue type instead of re-using mappings. You also can no longer click a button in Salesforce to trigger the creation of a ticket in JIRA.

Awesome connector for JIRA with customization easy to user

Awesome connector for JIRA with customization easy to user

Recommendation to improve

Service works great but the future method JCFS.API.pushUpdatesToJira should be changed to queuable type.

Great Service

Very easy to setup. The solution works great and the team is so quick to respond for any questions. In all my Salesforce career i've never had this great of service from a managed package. Highly suggest.

Does this work on Experience Cloud?

I want to know if I buy this for my client, can I use this to display JIRA issues on community pages?

Basic Function is good - Needs more flexibility

This integration is pretty solid out of the box and ServiceRocket's support is fantastic. It's missing some key function around permissions - We aren't able to put controls around who can create vs. view issues in Jira. We've put together work arounds but it's hugely important for a support process to have a clear path of escalation from via Support tiers. Salesforce housing some issues and escalation only via a technical team. This idea demonstrates the function missing: https://ideas.atlassian.servicerocket.com/ideas/VIS-I-8

Love the Ease of Use - Comes with a few deal breakers

Software is easy to install and work from most out of the box needs. As your Salesforce instance starts to become more complex and customized this software fails to meet those needs. The staff are aware of some of the basic limitations of their product and works toward trying to resolve the problems. The ideas website provided does keep a good running list of items that has been looked at but the development cycle falls short. It becomes quite frustrating to plan and implement changes when no clear priority is visible to the consumers.

Connected Remedyforce with JIra - recommended

This review was written to help anyone who uses Remedyforce but it also applies to 'Salesforce only' users. I picked this tool as a way to easily put Remedyforce incidents in to Jira and to be able to close them in Jira and they close in Remedyforce. Whilst it did take me a while to get every part that I wanted working the documentation is very good and the support (via email or Zoom) is excellent. The price of this product was very reasonable as well making it a great solution for our needs. I am able to insert issues automatically from Remedyforce to Jira and automatically assign them to a user in Jira. As the issue in Jira changes Status etc those changes are reflected in Remedyforce including when and issue is 'Done' in Jira it is closed in Remedyforce. 5 stars and thank you, ServiceRocket, for your terrific support. Recommended.

easy install and good concept but missing functionality

the install is not very complicated and there is good documentation available. I am missing some basic functionality like being able to filter a report in SFDC based on the tickets that were escalated into Jira. Also would like an option to add a label automatically to every ticket that is created in Jira from SFDC or associated to a case in SFDC. Also support can improve more.

Great Connector

Mapping is very nice and easy. Great support service. Needs some improvements on UI level in SF.