Likelihood to Recommend 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
Read full review The single element of Parature I've not seen in any other system of this kind is the Download Module. You can post files in the open, or protect them by any number of entitlement methods. The solution is also appealing to those who don't want to manage the back-end/IT needs as it is a hosted solution and has proven to be very reliable.
Read full review Pros Manageable workflow to ensure all users follow the same process. Can ban boards for easy visual of ticket status. Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model. Added communication tools help you get out of e-mail jail. Read full review Clean/Friendly UI. It was extremely easy to navigate around Parature's menus at a high level, and you could take advantage of the more robust features as you became more comfortable and familiar with how Parature operates! Strong Knowledge Base. Writing KB articles or ticket summaries and making use of the search function within Parature allows for expedient recovery of past ticket information. Being able to search for a fix action, or at least a troubleshooting article that can guide you towards a resolution is extremely valuable. Enhanced Notation Capability. Being able to send/post internal or external updates to a ticket is great! You can leave the wordy technical details for other employees while making sure to communicate the high-points and fix action to the end-user. Read full review Cons Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem). No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability. Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive. Request forms are very basic and there is no native dynamic field ability available. Read full review Reporting is barebones at best. If you need special reports, we had to go through Parature to have them built. The use of frames on a website is very 1990s. It actually impacts usability of the product, especially when combined with how Parature handled sessions. An engineer could only work one ticket at a time which, honestly, isn't very realistic for a busy support team that is working on several issues at a time. Support was often unresponsive when contacted for unplanned problems. The knowledge base was not very friendly for clients and it provided no real encouragement for it to be used. It took several clicks to do something as simple as edit and assign a ticket or to close a ticket. Read full review Likelihood to Renew Parature has been the best option for this campus in terms of what we use it for and there is no alternative
Read full review Usability I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.
Read full review 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.
Read full review Reliability and Availability 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.
Read full review Support Rating I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.
Read full review Nothing ever seemed to get resolved
Read full review Alternatives Considered When I evaluated
Spiceworks , it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did.
JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and
JIRA was the better option since it was less expensive and geared towards being a ticketing system.
Read full review There are services that do bits and pieces of what Parature does. We liked the idea of having one service that meets our needs
Read full review Return on Investment JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people. Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool. Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well. Read full review Parature allows for better Customer Service Can follow up automatically for tickets Will automatically close tickets that haven't been responded to. Allows customers to reopen tickets easily and not allow them to be missed. Read full review ScreenShots Jira Service Management Screenshots