Atlassian Crowd is a single sign-on (SSO) solution from Australian-headquartered software company Atlassian.
N/A
Jira Service Management
Score 8.0 out of 10
N/A
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…
In most ways, I preferred Duo Security as it offered a better 2-factor authentication method, and Crowd is definitely better than just having to rely on Active Directory.
I have always been of the mind to have a centralized server that sits between your active directory (azure …
For companies that are already using other Atlassian systems, then Atlassian Crowd will fit in very well. This is especially the case if the company is not yet big enough to use LDAP for user management, Atlassian Crowd can act as a temporary solution until the company outgrows it, as it is much easier and simpler than LDAP.
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.
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
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.
Overall, support is good, you get quick responses from Atlassian's official support system, and documentation is decent enough for you to find what you need.
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.
These products allow you to install them on your own infrastructure, so you can manage all aspects of them which can prevent you from getting throttled from API calls. When you hit a certain threshold of scale you may need to switch off of Atlassian Cloud to your own hardware. When you are a small startup, however, this product is probably a good starting point.
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.
New systems are tough when it comes to an ROI, as a dollar amount for saving time on a sign-in can be tough to track. Like most new systems that makes things slightly easier to execute as an end user or manage or support, it really might come down to the existing structure of how a company manages its users.
The positives are always with the end user, which I have to say, Crowd was able to accomplish.
