When comparing JIRA vs Axosoft, the Slant community recommends JIRA for most people. In the question“What is the best task management software for small teams?” JIRA is ranked 14th while Axosoft is ranked 33rd. The most important reason people chose JIRA is:
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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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...
Pro Helpdesk functionality
Turn emails into support incident tickets. A brandable self-service portal can be created for customers to create and edit tickets without using paid Axosoft accounts.
Pro Extremely fine-grained control over the lifecycle of each task
Tasks are divided into categories and each category can have one or more workflows which are followed by tasks belonging to that category until their completion.
In other words, workflows are used to set each step tasks need to take in order to be completed. Axosoft lets users have extremely fine-grained control over workflows and by extension, the whole lifecycle of each task. Each step in a workflow can be named and you can choose which fields are updated when a step is complete. This way you can automatically tweak tasks as they progress (you can set tasks to belong to different users once a step is complete, you can even change workflows for a task if a certain step is taken).
Pro Items can be exported as PDF
Each item has a PDF
button (among others) which lets you export all the information related to that particular item in PDF format.
Pro Allows you to view only the most useful information at a given time
Axosoft lets users pretty much create custom dashboards any time they want to view only a specific part of the project data and information.
You can choose which tabs to keep open and even how tasks are shown and what kind of data is shown for each task. This way you can see for example how much time is left in a sprint, or how much capacity the team has left to finish the project.
Cons
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.
Con Can get rather expensive quickly
Axosoft can get pretty expensive pretty quickly for large teams and/or large projects. The cheapest tier allows for a maximum of five users and costs $20/month. However, for larger teams and larger projects it can easily go into the thousands of USD per month.