Jira Service Management vs. Teamwork.com

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

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.

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

• I am a believer that simple and easy should be the key to create great opportunities.
• Teamwork has helped me to turn simple task management into the execution of large, massive projects.
• It has certainly worked great in helping to maintain workflow in my department.

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

• 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

Incentivized

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.

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

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.

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

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

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

• 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

Incentivized