When comparing Phabricator vs Pivotal 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 Pivotal Tracker is ranked 12th. 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.
While not perfect kanban, Pivotal is somewhat flexible in that you can mark sections of stories. So rather than (or in addition to) a normal sprint, you can put a marker in to define all cards above that point as part of something, for example a release. Further, you can override the auto tracker and define how many points in a sprint. So there is some degree of flexibility which sometimes you don’t find in “purist” agile or scrum tools.
Pro Great software to use in conjunction with a disciplined agile/scrum development philosophy
Pivotal Tracker has a Kanban feel to it, but takes a more opinionated “Agile” approach to feature management: It encourages items in the flow to be user stories with effort points associated to them to allow Pivotal to calculate your team’s velocity.
If you agree with the workflow, Pivotal offers a ton of functionality not provided by more generic tools like Trello. You can see your team’s velocity over time, organic smaller Stories into “Epics” (huge features) etc.
Pro Stories can contain media files
Easy to create features/bugs/chores with embedded files (screenshots, docs, videos).
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 Limited Work Flow & Process
Few story states. If your process involves some sort of QA and sign off, forget it - you get started, deliver, accept/reject, and finished. No way to customize this to your process. Sad miss for an easy fix/configuration.
Con Non-Editable Default Templates
Templates for defining stories and bugs save time. Pivotal has a default for story and bug. However you can’t edit these. So when you go to add your own, the titles can be confusing to users. Maybe title like “Our User Story” and “Our Bug”? Users will see all templates in the drop down and it’s confusing, so you end up with peope using the wrong templates which adds to process problems.
Con No Saved & Shared Views
Everything is in a column. Aside from destroying Kanban, it also gets confusing. The real downside here is that there’s no way to save a set of columns and pin for others to quickly see. Everyone on the team is usually looking at a completely different set of work. This is literally the definition of not being on the same page.
Con Not usable for multiple projects
If you want / need to have an overview of all the tasks going on over different projects and if you have these organized in different projects, there is no way to get an overview beside reporting. Just take a look at the screenshot and you see what you can expect.
Con No Kanban-board
To get a good overview often Kanban boards are used. You can somehow imitate a board, but it is not comparable to a real Kanban-board.