Autotask PSA is designed as a complete IT Business Management Platform for MSPs, now from Datto (resulting from the Autotask merger with Datto in 2017).
N/A
Jira Software
Score 8.0 out of 10
N/A
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Datto Autotask PSA is probably the best all-in-one platform for MSPs. It's targeted and designed specifically for MSPs, whilst most service desk software/PSA is often just general service desk software.
Autotask is more robust than simple ticketing systems. It provides better billing ability that many ticketing systems and works well with existing clients. The invoicing options provided are beneficial to the business and streamline the process. The ticketing system provides …
In my opinion, Datto Autotask is exceptionally complicated to set up, manage, and use on a daily basis. I would think the target market for this product would be someone managing a team of 20 - 50 people, possibly more. In my experience, for it to run properly you will need to dedicate at least half an FTE to running this product in an organization of that size per month. I would not recommend it for companies with less than 10 people or for companies that value quick communication with their clients. I would not recommend it for companies using Datto's RMM product. The integration exists, but it is clearly a bolt-on. They were not developed together and they are slow to talk to each other. Frequently you cannot add details from RMM sessions into the PSA without manually copying the ticket number, and if the ticket is more than a week old, then you can't even find it with the ticket number.
The Jira software works well for managing scrum boards and allocating resources to a task. When your Epics and Issues are set up properly, it can give you a good idea of where your team stands and the trajectory of your project. It is not the ideal solution if you need to provide documentation and support to people outside of your product teams or organization. It would benefit from having a public documentation or repository feature.
The graphical calculations on time spent on requests, how long they were open for, who worked on a ticket last.
Grouping by priority so you can determine easier what needs to be addressed sooner rather then later. This also helps if Account Management has conversations a technician is not aware of so they can prioritize efficiently.
The email updates that are sent out to the technicians so they are aware of upcoming or stale tickets.
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.
Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
The portion of Autotask that we've used other companies for prior to using Autotask is the Endpoint Management. The Autotask Endpoint Management (AEM) portal integrates perfectly with their PSA/CRM tools. It's alerting features are much better than the above software as there aren't a bunch of superfluous and unneeded alerts. Instead, it only alerts for things that you specify that you want. Alerts aside, for the PSA/CRM, I don't have much to compare it to as Autotask was the first PSA we tried. It's hard to imagine a PSA having more features or doing a better job than Autotask.
Jira Software has more integrations and has more features than many of its competitors. While some of its competitors do have better UI/UX than Jira Software, they have improved this greatly over time. Atlassian also acquired Trello years ago, so that adds better user interfaces to the system. They do also offer a pretty in-depth library of how to customize the platform that others don't.
