Jira Service Management vs. Statuspage

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

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.

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

• Interface is very intuitive and easy to use with very little training.
• Ability to customize messaging for events and notify before, during and after maintenance.
• Integrations with app like Twitter and Slack.
• Ability to automate all our maintenance notifications.

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

• I wish I had more ways to customize the layout.
• I wish I could show custom date ranges when looking at historical up-time.

Incentivized

I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.

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.

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.

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

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

• Helps organize communication to our clients during an incident.
• Demonstrates our level of transparency to prospects.

Incentivized