Jira Service Management vs. Microsoft System Center Service Manager

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.

Incentivized

We use Microsoft System Center Service Manager in the education sector. We believe this is the only real way to manage our IT systems and ensure compliance for not only today but tomorrow as well (what ever that brings!) Our IT management team significantly streamlined our working practices to mold a slick IT support service which serves our end users efficiently. Microsoft System Center Service Manager brought added automation and clarity for all major stakeholders in our organization through detailed reporting and scheduling, ensuring a complete realtime picture of the IT estate.

Incentivized

• 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

• This tool is used to track support requests among our IT staff.
• We use this tool to automate some more routine tasks.

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

• The software requires a lot of memory to run smoothly, otherwise it will be slow.
• It takes some time to learn, and training prices are a bit high.
• The price is a bit high; System Center is not a cheap solution.

Incentivized

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.

Incentivized

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.

Incentivized

As with all software, Microsoft System Center Service Manager has its quirks but it has more than made up for them with the sheer amount of functions the system brings to the table. Being based on the ITIL framework really shows with its design/terminology and, generally, we have found it 'just clicks' with our ITIL trained staff which makes operating our system straightforward and enables us to report to end users and all stakeholders consistently with ease.

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.

The customer support service is excellent. They help from start/deployment through to any time later on. They responded quickly and resolved our issues professionally and in no time.

Incentivized

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.

Incentivized

I can't really compare them as we haven't used an "all in one" tool like SCCM. There are other patch management software, other remote control applications, and to be honest, I find those work better when compared to SCCM. However, there hasn't been an application yet that does it all, so I feel it's unfair to compare. All of these tools that SCCM offers could/should be fine-tuned and made to be a bit more user-friendly.

Incentivized

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized

• The tool has saved money in a transition from another 3rd party tool
• It simplifies the ease of use for users. This is similar to other Microsoft tools
• We are able to provide reports of system performance when questions arise about availability.

Incentivized