When comparing JIRA vs FogBugz, the Slant community recommends FogBugz for most people. In the question“What are the best bug/issue tracking tools for small development teams?” FogBugz is ranked 6th while JIRA is ranked 16th. The most important reason people chose FogBugz is:
Customers can send emails for further processing.
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 features
Customers can send emails for further processing.
Pro Evidence-Based Scheduling
EBS produces ship date probability distributions, see here.
Pro Backed by big company
The same company behind Stack Overflow and Trello.
Pro Intuitive UI
The UI is very well thought through. All the right stuff is in the right places.
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 Self-hosting is pricey
The minimum is 50 users at $15 per user per month.
Con Cannot be used without an account
You cannot show someone a ticket that does not have an account.