When comparing TeamWork.com vs JIRA, the Slant community recommends TeamWork.com for most people. In the question“What is the best task management software for small teams?” TeamWork.com is ranked 6th while JIRA is ranked 15th. The most important reason people chose TeamWork.com is:
Tasks are grouped in task lists and can have subtasks. Each task list can be assigned to a particular set of users, aligned with a milestone and have notes. Each task in the task list can have a description, a start and a due date, attachments, priority, manually set progress, followers, dependencies, be assigned to a particular set of users and set to repeat. Each subtask has the same configurable properties except instead of the ability to assign people, subtasks can be commented on.
Ranked in these QuestionsQuestion Ranking
Pro Offers lots of granularity in task management
Pro Each project has only the required functionality
It's possible to limit projects only to the necessary features so that unnecessary functionality doesn't get in the way and clutter up the interface.
Pro Good assortment of features
Gantt charts, calendar and an easy overview of huge amount tasks.
Pro Lots of integrations and plugins
It integrates well with a lot of other tools, including other products from the Atlassian suite. Plus there are a ton of plugins, including charting tools, screen capture, etc.
Pro Backed by a trustable company
Jira is developed and maintained by Atlassian, which is not an unknown venture, especially for developers. Atlassian has a great number of other products used by million of users worldwide, including BitBucket, HipChat, Confluence and Stash.
Each of these products have hundreds of thousands of users who use them daily and this has allowed Atlassian to garner a lot of goodwill from the dev community.
Pro Very cheap for small teams
Pro Supports version-focused work-flows
JIRA is not a plain long list of tickets, but can be configured to be version-focused, so planning and understanding the progress in a software project becomes clear.
Pro Great reporting tools
Jira offers amazingly powerful reporting tools like activity stream, different graphs of opened and closed issues over time etc...
Con Provides too much detail for small projects
Amount of granularity for tasks can be overwhelming for small projects or teams.
Con New releases often change the GUI largely
Sometimes the usage becomes worse, e.g. when creating a new ticket, you need to click the notification to keep it on the display.
Con Locks you inside its own ecosystem
If you use Jira you are pretty much locked inside their ecosystem. For example, if you want to add a tool to your project management stack (like a wiki) more often than not you will have to buy one of Atlassian's tools.
Con Client application support
No free client applications; IDE connector development was discontinued. Users are effectively locked into using web interface which requires context-switching.