Freshservice vs. Jira Service Management

Freshservice is a complete ITSM solution. I have used some others over the years and moved away from them to Freshservice. I have implemented Freshservice in 2 new roles over the years, and everyone has loved it. The functionality that it incorporates, enabling IT teams to become ITIL compliant is truly useful. Compared to 5 other ITSM tools that I have used over the last 10 years, Freshservice is far better.

Incentivized

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

• Workflow automation
• Knowledge base articles for users and agents
• easy to add categories & sub category and make them compulsory so that ticket cannot be closed without filling the information
• it works with email address very simple to create different department and queues

Incentivized

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

Incentivized

• Change Management - Current system is geared towards full software or system change management. It would be great to have a simple Yes/No approval without having to utilize their workflow tools.
• Data selection filters - Overall, their data filters are very good, but it would be useful to have "Last Week" and "Last Month" in the date selectors.

Incentivized

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

Incentivized

It's overall value in our organization is extremely high and it has become an essential part of our business.

On the I.T. side, the time to ramp up and understand how FreshService operates only took a few hours. After that, it was off to the races with configuration and customization. From the start, with minimal assistance, our end users found FreshService to be incredibly intuitive. At launch, we expected most to submit tickets via email, however, our analytics has shown that end-users actually prefer the portal for managing their I.T. tickets.

Incentivized

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.

I contacted support once and the person handling the request was very helpful. The staff is very competent. In my opinion communication could be improved as the level of spoken English is very high. I was unable to understand some words, in fact two people participated in the second meeting.

Incentivized

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.

Incentivized

think of what you want to do with FreshService : a clean start or a migration. Migration can be done with csv files, it's easy to do but you need to test it first.

Incentivized

I've used monday.com for ticketing, but Freshservice is made for it and the asset management feature adds value. NinjaOne's ticketing is not built out so we only use it for its RMM features. Atera has a nice ticketing platform and looks similar to Freshservice but they do not have an onboarding feature and other integrations that Freshservice has

Incentivized

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.

Incentivized

• Freshservice has allowed our organization to better track the amount of tickets that come in for a particular individual. This allows us to better support a user that is having multiple of the same issue over an extended period.
• The communication to the user has greatly increased due to the automated messages that Freshservice has built in.

Incentivized

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

Incentivized