Jira Service Management vs. Parature (Discontinued)

Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up

Parature earns a "7" on my rating scale because it fits the bill for a ticketing solution. While it is not the most powerful utility I have come across, it is fairly user friendly and gets the job done. There is quite a bit of room for customizing the interface, but it comes with a learning curve. A score of "7" reflects what I would tell anyone who is looking for feedback on this application; it's better than a majority of the market share, but still has room to grow!

Incentivized

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

Incentivized

• Syncs all support emails into cases that can the be prioritized, monitored, and tracked.
• Provides easy canned responses to common support questions helping save time.
• Provides live chat.

Incentivized

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

Incentivized

• Implementation- I think they have worked on improving this since we launched
• Custom requests
• Perhaps an interface with other business systems

Incentivized

We left Parature for Salesforce Service Cloud. While Parature was functional, as our business matured we needed better support, more stability, and a lot more features. In addition, it integrated with our sales, marketing, and finance department, allowing us to all use a single solution and be able to share information across departments.

Incentivized

I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.

Incentivized

It was bulky, cumbersome, and didn't allow us to handle the volume of cases we received on a daily basis. Many of our issues were highly technical in nature and we would often need to work on 2 or 3 at once. The poor design choices prevented this, which was unfortunate.

Incentivized

They recently had one very extended outage. It was a data center issue - but they were not diversified enough so in the end the system was down for almost 8 hours. There are also periods of time where for no reason the system simply doesn't respond. This small outages are usually short (just a few minutes), and have in fact been occurring less often, so it appears some corrective actions have been taken.

Incentivized

I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.

Nothing ever seemed to get resolved

Incentivized

We chose Jira Service Management due to its easy integrations with the rest of the Atlassian tools, as we have also invested in those. For the price, the ability to add or remove agents, and the cost being reflected in that, it was an excellent medium for us. For the foreseeable future, I do not see us moving off this platform.

Incentivized

Before choosing Parature we reviewed many of the currently available solutions before building our short list of Parature, SugarCRM, Zendesk, Salesforce, and NetSuite. In the end, the licensing models for Salesforce and Netsuite eliminated them from consideration. The SugarCRM solution was our current solution, and didn't appear to be a key area of focus for Sugar (though we continue to use SugarCRM for everything except the Ticketing feature). Zendesk lacked the Download Module feature which is a critical element of our deployment. In the end, it was Parature that addressed all of the needs we identified and did so in a single, hosted solution. It was also one of the least expensive to deploy and maintain.

Incentivized

• It has allowed us to take on a larger volume of work at a faster pace.
• We have established best practices with the tool that we have taught and sold to clients.
• It has allowed for further collaboration with a larger team.

Incentivized

• Positive: everything is housed in one place, we are paperless and we are efficient.
• Negative: the bugs of this product make the above equally as frustrating. Also, some people don't use it correctly and going back and fixing their mistake is time-consuming. The reporting feature are also pretty flawed.

Incentivized