Freshservice vs. Jira Service Management

Tickets are easily passed between teams and departments which makes for a much better user experience as you can easily pass a ticket over with comments to work colleagues in other areas whilst keeping the ticket and communication with the customer seamless. Automating a lot of our tasks for instance getting PRTG to report and assign to specific staff based on criteria works like a dream and mean incidents are tracked right from PRTG and reportable against.

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

Jira Service Management tool will serve it's purpose to do what it is meant to be. It has it's own limitataions on few features, however it's the industry standard ticketing tool. All covers all the processes that required to resolve the issues. It has various use cases in incident management, Request management etc.

Incentivized

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

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

1. Cost - I have always had the best cost provided by Freshservice as compared to others 2. Functionality - far more functionality is provided by Freshservice 3. ITIL enabled ITSM tool with better support for different ITIL modules 4. Reporting - easiest to produce reports in Freshservice 5. Workflows - Workflows are far superior and easier to configure as compared with other products Service Now is great for the above as well, but it comes at a far greater cost as compared.

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

• Our President is able to look at ticket loads, statuses, and urgencies of requests. This has helped him oversee the IT department.
• Moving from managing requests and issues reported in emails and MS Teams to Freshservice has increaesed productivity exponentially.
• Being able to respond to users via email within the ticket has helped track communications, and the internal comments section helps IT staff and managers discuss the tickets and document approvals.

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