We performed a comparison between JIRA Service Management, OpenText Service Manager, and ServiceNow based on real PeerSpot user reviews.
Find out what your peers are saying about ServiceNow, Atlassian, BMC and others in Help Desk Software.
"I think one of the most valuable things is that it's all integrated."
"Jira lets us customize the workflow to meet our requirements. The email and alert features are also handy."
"I find the Kanban chart where we put each story in to be the most valuable feature. We use the Kanban chart to revise the project every morning in our five-minute meeting."
"I'm mainly working in the ITSM module of JIRA Service Management, and the integration between the system incident and how you can link all the records to the change makes it quite powerful."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"Some of the most valuable features are simplicity, ease of configuration, and ease of customization."
"A good organizational tool."
"The customer portal with connection with our knowledge base has been most valuable."
"Sometimes, customization is simple. The version we are using now has a nice interface."
"We can have all our requests and incidents registered in one system."
"Its flexibility and ease of customization are its most valuable features."
"It helps to register things, to see the changing parts, and to correlate incidents."
"The initial setup is easy."
"Incident management is the most valuable because we're using it to manage tickets for an accounting system. With the reports that are available, it allows us to track and identify trends at the type and item level. It also helps us in managing the workload better than what we had in Remedy, which is what we were using before 2013."
"The workflow engine that standardizes and globalizes the process steps. It drives people through the process by standardization and automation."
"Technical support is pretty good."
"It's easy to integrate. For instance, yesterday we closed the integration with SAP for the IP business management module to manage the forecast of projects. We created an interface between ServiceNow and SAP to control projects for accounting and on the forecast of the project. It was really easy. We don't have any problems with ServiceNow at the moment. As a company, they are improving constantly."
"It's more about the ease of use of ServiceNow. Plus, everything is there in a single platform. If you need any additional functionality, you just need to enable the plugins without even installing anything on the servers"
"There are many expansions available."
"Your time-to-market, or TTM, becomes faster when you use ServiceNow. Even individuals that are not tech savvy can quickly change processes and workflows in it. This can make the organization as a whole more agile."
"I like that it's always up and running."
"ServiceNow is easy to use."
"I have found the workflows and integration the most valuable in this solution."
"The product's integration functionality in the change management module has significantly improved efficiency in our organization."
"JSD has some analytics, but it's pretty much basic and simple dashboards. There's no mobile application for JSD. It really would benefit from better implementation with other vendors. We're heavily reliant on some external marketplace applications."
"The solution should be more formalized. It could be more user-friendly."
"There is no notification regarding language upgrades."
"The solution needs to be integrated better with Office X5."
"Lacks an interface where the customer can report issues."
"Every time there's a problem with JIRA Service Management, you have to have a look at how to solve it, and there's always a feature request or the feature request on the solution is too large and the development cycles are too slow."
"With Jira, we were unable to implement time-based automation in its ticketing system. We would like a feature where we can define tickets based on severity, then tickets are automatically escalated to the next level after a set period of time if they go unanswered."
"I don't think the program is very scalable."
"I think one area which is the most painful from my point of view is if you need to integrate a lot of the tools, and being able to make that a lot more seamless."
"With the new version moving toward the codeless configuration is good, but it's losing flexibility."
"It needs to be easier to use for the end users because one problem we had was that we are handling different kinds of cases."
"Service Manager is at the end of its life. The architecture, performance, and look are all way behind."
"We aren't able to take emails that come in and turn them into tickets, especially when it comes to attachments. When an email has an attachment, like a screenshot, it is a very cumbersome process, and it does not work very well. I shouldn't have been paying technicians to cut and paste attachments from an email into the ticketing system. It should do that automatically. Other solutions are able to do that. This is something that needs to be improved. Test manager and knowledge management areas are probably amongst the worst parts of this solution. We try to use this solution for knowledge management, but it is not user-friendly. Therefore, it has limited ROI as you need to spend time to try and fully capitalize on the knowledge management system."
"I don't see anything lacking."
"The user interface is very clunky. It's only now beginning to be a web-based interface, but for now it's still very clunky."
"The solution does not interface well with other products and is difficult to implement."
"It's a great platform, but there's still room for improvement. As the solutions stands now, you do need a lot of previous experience to use it. It would be great if they could develop some use case templates. This would be beneficial for a small and medium-sized businesses."
"Integration capabilities can improve."
"There's always a room for improvement in terms of the ServiceNow UI. For customers, the UI is something that is a continuous improvement."
"The installation and deployment of ServiceNow can be a bit challenging. One major issue I've encountered is that ServiceNow doesn't provide the same mobile responsiveness or features that we used to enjoy with other tools. For example, with Splunk, our response times were about five minutes, and we could manage alerts and incidents directly from our mobile devices."
"They could improve license management, particularly when integrating different applications or toolsets."
"When we are using the solution on mobile phones on their networks the performance is reduced with a delay of approximately 8 seconds. There is less delay using the desktop computers connected to the WiFi or to the network directly."
"There are Virtual Task Boards in the tool in the latest releases. There are many of them in the Scaled Agile Framework. There is some room there for improvement. It's really quite promising but, at the same time, it could be improved and I believe it will be improved soon."
"The level of complexity and the level of discovery are the two areas that can be improved. Its UI needs to evolve. They focus a lot on cool colors and other little things, which don't bring value in terms of functionality. They need to focus less on presentation and more on the functionality within the UI. Its discovery mechanism should be improved. There is a component in ServiceNow that discovers the assets, but it doesn't do an immediate discovery, and there is a lag. If I want to open a ticket for a laptop or an asset, that asset needs to exist within ServiceNow for me to be able to say that I need to have its disk space or memory increased. It is referred to as a CI or configuration item in ServiceNow. Sometimes, ServiceNow doesn't discover these items, and as a result, I cannot open a ticket and tag that system or asset. If a system was introduced to the environment last week and it is still not listed, it becomes a problem. I will either have to wait or manually enter that system or asset. So, if I have a laptop with only 8 GB of memory and I want to request 16 GB of memory, I won't be able to do that in ServiceNow because my system or asset hasn't been discovered yet. Discovery is not immediate, and there is a lag."
