When comparing Phabricator vs Bitbucket's bug tracker, the Slant community recommends Phabricator for most people. In the question“What are the best free bug-tracking tools for programming? ” Phabricator is ranked 3rd while Bitbucket's bug tracker is ranked 5th. The most important reason people chose Phabricator is:
Phabricator is completely free and open source. It's source code is hosted on [GitHub](https://github.com/phacility/phabricator/).
Ranked in these QuestionsQuestion Ranking
Pro Free and open source
Phabricator is completely free and open source. It's source code is hosted on GitHub.
Pro Actively updated
Phabricator is quickly improving, with bug fixes and new features added often. There is an update to the changelog every couple of weeks.
Pro Bug tracker is included
Includes a bug tracker out of the box. Allows for managing bugs, creating issues, commenting on them and closing them.
Pro Supports the three major version control systems
Support for Git, SVN and Mercurial is available.
Pro Super flexible bussiness rules (Herald)
Pro Able to review graphical asset changes as well as code.
Pro Built-in Wiki and pages support
Pro Fine grained access control
With using Spaces and Project and custom policies you can have any combination of access to any object inside of your own Phabricator instance.
Pro Designed by software engineers for software engineers
The engineering workflow is far superior to Github style branching and merging. Phabricator separates local representations of the repository from remote, which enables a variety of workflow optimisations, like stacked diffs on a single branch.
Pro Built-in Q&A platform - Ponder
Instead of having to have separate Q&A tool, there's Ponder which takes out the hassle.
Pro Code ownership
Users can subscribe to files or even repositories and notifications will be sent when code you are subscribed to is changed.
Pro Command Line Access (via arc)
Pro Able to track design mockups
You can track not only code bud also design mockups.
Pro Built-in voting
You can create voting in an instant and need not to rely on external tools.
Pro Built-in blogging platform
There's a great platform which you can use to post stuff, or use as an internal blog, dev blog, release anouncement place and many others.
Pro Built-in Chatrooms
Pro Able to manage legal agreements for open source projects
Pro Fully customizeable workboard
You can configure your workspace to deal with tasks, bugs, todo's, etc.
Pro Free unlimited private repositories for small teams
Bitbucket offers unlimited private repositories for free, as long as the number of members in a team is not larger than 5. BitBucket does not use GitHub's pricing plan, instead of charging users for each private repo, it charges teams per number of team members. It is free for up to 5 people.
Pro Supports both Mercurial and Git
Has full support for both Mercurial and Git VCS.
Pro Native application for both Mac and Windows
Atlassian, the company behind BitBucket is also behind SourceTree, a free application for Windows and Mac wich works as a client for both Git and Mercurial which can be connected to BitBucket and other code hosting services.
Pro Multiple authentication methods
BitBucket supports GitHub, Twitter, Facebook, OpenID, Google and even GitHub authentication.
Con Difficult to configure
Compared to a solution like Bitbucket Server (granted Phabricator offers more options), it is difficult to configure. Settings are scattered everywhere and you must drill down through several screens to find some of them. Documentation is very complete but also not always in parity with the application itself.
Con Only 5 users are free
5 users free: Unlimited private repos, Dedicated support, Code reviews, Custom domains, JIRA integration, REST API.
Con Integration with other tools is not as good as github
Most of the 3rd party tools ( bug trackers, CI servers, chat servers, etc) always integrate with GitHub first, and either don't integrate with Bitbucket at all or do sub par job in it. For example there are 3 separate projects to allow building and verifying pull request submissions on Jenkins CI server and there is only one viable one for BitBucket and that one is really buggy and lacking many features.
The only exception to this rule is Atlassian products like Jira.
Con The UI seems old and not very polished
While GitHub's UI is extremely simple to understand and very polished, BitBucket lacks a bit on this category. With a design that seems old and not as pleasant to look at.