Jira Service Management (Jira Service Desk) vs Salesforce Service Cloud

• Highly configurable Notification Scheme, allowing free customization on who receives notifications and when
• Ability to add extra features through the highly diverse Atlassian Marketplace.
• Simple and highly customizable ticket interface. The Software can be almost completely branded in every aspect to represent your organization.
• Integration with Jira Software allows support tickets to be moved into other Log Term projects as necessary.

Read full review

• Flexibility of data tracked, displayed, reported on, and customized.
• Single source of truth for support, implementations, sales and management.
• Ability to integrate through built-in app exchange and easy API.
• Reporting and emailed reports with direct links to drill down into data.
• Do virtually whatever you "need" to do.

Read full review

• Some of the built-in functions and workflows are surprisingly limited given the fact that you can customize a lot with JQL. These limited areas do not allow you to use JQL. For instance, the built-in notifications are lacking. They have one that is great-- "notify on critical ticket creation"-- EXCEPT that it does not allow you to notify a group or anything, only individual users.
• The ticket interface is a little odd for agents. Changing the status is not a simple drop down from unassigned to open to in progress to pending, etc. There are a couple of tabs ("investigate", "pending", "workflow") where you can change the status in different ways. Maybe I am just not used to this way of doing it, but I feel like it could be simplified.
• It can get complicated deleting/changing some of the out-of-the-box fields and rules, because you never know what will break workflows or other automated/built-in features.

Read full review

• Incredibly complex to set up and configure.
• Multiple points of potential failure.
• Things Desk.com did out-of-the-box require customized code and components in Service Cloud.
• Front-facing community is extremely difficult to configure and comes with many limitations.
• No help is provided by Salesforce without expensive Premiere Support plans.
• Expensive! Hidden costs and development costs are going to make Service Cloud far more expensive than almost any other Help Desk provider out there.

Read full review

• We would not be very organized as a software company without using JIRA and it would in turn reflect negatively across the entire studio and the products that we release.
• Almost everyone in our company uses JIRA in one way or another from developers to testers to marketing and every team in between.
• The only time I have witnessed that JIRA has a negative effect on our objectives is if they suffer a major failure on their part and JIRA is not accessable or usable for a length of time. Thankfully in over 3 years of using JIRA this has only occurred a handful of times.

Read full review

• While I don’t have a dollar value because I’m not the manager of the support team, I have heard many accounts of how the use of Service Cloud has made us much more efficient at delivering customer support
• Using Service Cloud has had a big impact on removing silos between departments because it’s much easier now for non-support users to interact with cases
• We now have a lot of automation of other features that we didn’t have before Service Cloud, for example, integration with our customer survey tool

Read full review