Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
$0
per month
ServiceNow Now Platform
Score 8.9 out of 10
N/A
The ServiceNow Now Platform is a digital workflow building and extension tool for ServiceNow featuring a number of low-code / no code tools.
N/A
Pricing
Jira Service Management
ServiceNow Now Platform
Editions & Modules
Free
$0
per month
Standard
$20
per agent/per month
Premium
$40
per agent/per month
Enterprise
Contact sales team
No answers on this topic
Offerings
Pricing Offerings
Jira Service Management
ServiceNow Now Platform
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Jira Service Management
ServiceNow Now Platform
Considered Both Products
Jira Service Management
No answer on this topic
ServiceNow Now Platform
Verified User
Program Manager
Chose ServiceNow Now Platform
ServiceNow was chosen as replacement for Microsoft Project , due to better licensing model, more flexible configuration of the project stages and components, better API with Azure DevOps. Also ServiceNow is best in the area of Incident and Service management systems and the …
I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.
ITSM is straight forward creation of Incidents and Requests. It can get more confusing as you layer more modules on top of it with event management, risk, project, etc. It also becomes more costly as everything is a different license. Integration between other external applications is very easy to do with their API. You can easily create endpoints for external apps to talk to or create REST messages for the platform to reach out directly.
Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
Allow multiple different entry points and work flows for as many different needs your teams / company have
The ServiceNow performance speed has big room for improvement, as it is quite slow in loading Dashboards with more than 5-6 widgets. We are keeping our ServiceNow version up to date with latest releases.
Usually there are issues with having multiple ServiceNow tabs open in the browser and have different dashboards open in those tabs.
The way of showing a history log of all activities on Incident ticket is not optimal and easy to use or search in and have very old design.
In the current contect the requirments is around having a tool that is focused and can handle large ticket volumes and tracking incident, problem and user requests concerning end users. Jira has built in functionality to address the above practice needs faily easily and has a substantial amount of customizable reports for generating the relevant intelligence.
While we are very likely to renew, we are also assessing if we should renew all of what we currently subscribe to as we try to reduce costs. Some parts of the business feel there may be a better tool out there to fit their process requirements. We are currently working with them to identify what those requirements are to see if it makes sense while also pointing out a reduced cost of tooling is not always the best fit if we have an increased cost of customization and maintenance between tools.
If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.
It provides a lot of modification options which is wonderful for certain team usage but becomes too much of a job when it comes to the Service Desk. Also on the app support side, since too much information can be carried, it affects the GUI and makes it complex.
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.
I was not in the team that take care of the installation of ServiceNow but their feedback was very positive. Go live was done by the planned date and their support at the beginning provided always a timely response. Their customer service is friendly and easy to reach. Today we don't use their customer service anymore because we have an internal IT dedicated to maintaining the system.
We went through a re-implementation last year with a partner and were very pleased with the outcome. We looked at several partners and chose one that was able to provide an entire scope and cost upfront of what would be required to complete our requirements. We worked very closely with the dedicated team assigned to our project throughout the process and they fully delivered on all of our requirements that we presented in the initial scope.
Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.
I've used Freshservice which is very similar to ServiceNow. I can definitely say ServiceNow performs better in a larger environment. Freshservice is usually used in smaller organization or less complx environment. Plus the ServiceNow reporting and dashboard features are more accurate than Freshservice. ServiceNow is a bit costly but gives way more features that really helps my organization.
1. It is not great when they can't seperate apps/products from a particular sku, forcing you to make a business case for a larger portion of functionlity than your current business case seeks to address. 2. ServiceNow reps are able to work with you when economies of scale are projected out. They are willing to start at a desired tier and provide pricing at applicable upgraded tiers
Very easy to use. Capture more data from the Incident and problem management. Easier to escalate and following the change management process to resole the issues.
Fast implementation of our Sales & Operation/Projects controls and process - tool adapted to our needs, not us to adapt to the tool.
Once we are a consulting/implementation company, our customers are happy to see that we use what we sell, and it is easy to show them how this platform/tool can have an impact on our own business.
