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
Teamwork.com
Score 7.8 out of 10
N/A
Teamwork.com is a project management platform built specifically for client work. The platform helps users deliver work on time and on budget, eliminate client chaos, and understand profitability. Teamwork.com’s customers track and manage their projects with a suite of integrated solutions such as helpdesk, collaboration, knowledge sharing and customer relationship management add-ons, enabling Teamwork.com to be the ‘one-stop shop’ solution for business owners. Headquartered in Cork,…
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
Teamwork is awesome for teams who need a flexible tool that supports all types of projects. Since it supports kanban it makes visualizing the work to be done and the work in progress very easy. The Gantt chart support is decent and helps to understand how a team is doing when it comes to getting work done in a given time frame. Teamwork isn't a great option for companies that have a bunch of projects going simultaneously due to the way Teamwork structures their billing based on a number of active projects.
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.
Visualization needs to be improved, charts graphs are limited
Value stream mapping should be available to determine and prioritize the work.
Documentation should be available stepwise with export and printable facility.
It should be configurable like ERP with cross functionalities of different users, where users login, assign and approve the work, job or project details, where it should be collectively effected on a project.
Add many examples, little more AI, Machine learning required for suggestion and recommendation. It would be a plus point
We are already at an annual contract, and have been for the past 5 years; so far the system has delivered, and our personal is already trained in it. A major overhaul of our entire infrastructure (as in moving everything to a single, unified platform) might change the current continuity of Teamwork Projects on our organization, but that's not feasible in the near future.
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 give it a 9 out of 10, because there is a bit of a learning curve when you first start using Teamwork Projects because there is a lot to learn & recognize where to find it. They do offer a good range of tools that can be applied to every project - So say you're working on an internal project and don't need Milestones or Billing, you can shut those modules off. This can help simplify the interface for beginners. Once you've had a few days in Teamwork Projects, I think it's a 10/10 usability. It's very easy to accomplish your tasks and keep track of what you're managing.
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.
We've been able to meet with the customer success team on multiple occasions to discuss the roadmap and learn about the company culture. Being based in Ireland, we occasionally have to wait until they wake up to get support requests handled in the states and larger conversations about big enhancement requests were politely collected but not followed up on
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 spoke about this quite a bit before, but as far as usability goes, Microsoft Projects is totally useless for me, so I avoid it at all costs. Basecamp was just a task management app and had very small feature set beyond that. We had to rig it to do other things for us, but it failed at that. Asana was a very nice app to trial, but it lacked many of the features that we were looking for.
Teamwork was a great starter into project management software. We were WAY more organized and efficient than we ever were with Trello boards and the PM software included with our accounting system.
Clients were mostly pleased with interacting with Teamwork, and appreciated the ability to track their comments and requests in one place.
Ultimately, we stopped using Teamwork after about 6 months because we need something more focused on web development projects specifically
