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
Statuspage
Score 9.1 out of 10
N/A
Atlassian Statuspage provides status updates for shared cloud resources to users, eliminating duplicate support tickets and displaying uptime status.
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
StatusPage is well suited for notifications on services and products. If you need to have a passive way to notify users, internal staff, or executives on the status of SaaS services, StatusPage is a low barrier way to do this with minimal setup and maintenance. StatusPage is not well suited for scenarios in which you want info kept private. If StatusPage is updated, the subscribers to those alerts will be notified so you just want to make sure you're addressing the right audience with updates.
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.
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 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.
Support is very responsive although we haven't had to contact them in a time of emergency, all of our support inquiries were answered in a timely manner and usually resolved with their first response. Support responsiveness played a big role in our decision since if we need help during downtime, we can't really afford to wait.
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.
I would say StatusPage on its own is a great service. StatusPage for Hipchat can only be used with that specific chat client. But on its own StatusPage can be integrated with many tools, like Slack, email notifications, text notifications, etc. I don't know of a tool that compares with StatusPage. You could essentially host your own status site with Greed Yellow or Red statuses, but you would be missing out on the robustness of a tool that keeps historical data, uptime, and segregates services based on components.
