When comparing Quire vs JIRA, the Slant community recommends Quire for most people. In the question“What is the best task management software for small teams?” Quire is ranked 13th while JIRA is ranked 14th. The most important reason people chose Quire is:
Free for up to 10 team members.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Free version
Free for up to 10 team members.
Pro Integrations
GitHub, Slack, Microsoft Teams and Zapier integration.
Pro Multiple assignee
Assign to more than one person for a task.
Pro Kanban Board
You can move some selected tasks from the list to board to get focused.
Pro Simple and elegant UI
Everything looks clean and easy to use.
Pro Nested task list
Task list with unlimited subtasks.
Pro Flexible permission control
Assign to external team, share link with clients without signup, control members' view.
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...
Cons
Con Not self-hosted
Not available as a self-hosted solution.
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.