Atlassian Crowd is a single sign-on (SSO) solution from Australian-headquartered software company Atlassian.
N/A
Jira Service Management
Score 8.1 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.
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
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.
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 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.
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.
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.
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.