Phabricator vs Redmine: What are the differences?
Developers describe Phabricator as "Open Source, Software Development Platform". Phabricator is a collection of open source web applications that help software companies build better software. On the other hand, Redmine is detailed as "A flexible project management web application written using Ruby on Rails framework". Redmine is a flexible project management web application. Written using the Ruby on Rails framework, it is cross-platform and cross-database.
Phabricator and Redmine are primarily classified as "Code Review" and "Project Management" tools respectively.
Some of the features offered by Phabricator are:
- reviewing code before it hits master
- auditing code after it hits master
- hosting Git/Hg/SVN repositories
On the other hand, Redmine provides the following key features:
- Multiple projects support
- Flexible role based access control
- Flexible issue tracking system
"Open Source" is the primary reason why developers consider Phabricator over the competitors, whereas "Open source" was stated as the key factor in picking Redmine.
Redmine is an open source tool with 3.41K GitHub stars and 1.86K GitHub forks. Here's a link to Redmine's open source repository on GitHub.
Weebly, WebbyLab, and Coach United are some of the popular companies that use Redmine, whereas Phabricator is used by Facebook, Dropbox, and Coursera. Redmine has a broader approval, being mentioned in 72 company stacks & 34 developers stacks; compared to Phabricator, which is listed in 52 company stacks and 12 developer stacks.
What is Phabricator?
What is Redmine?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Phabricator?
What are the cons of using Redmine?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We were using a hosted version of Redmine to track defects and user stories originally. We migrated to Jira.
Jira was an easy decision for a number of reasons:
- It's much more "Scrum ready" straight out of the box
- It's so much easier to keep a track of progress (I love the reporting)
- It natively encourages you to adhere to Scrum/Agile/Kanban practices
- Atlassian has a fantastic DevOps ecosystem when considering the likes of Confluence and Bamboo etc
- So many integrations!
- Its UI is so intuitive which makes it an absolute pleasure to use!
I know there are alot of other tools in this space but not even considering anything else at the moment. Love Jira!
Our team has been using Redmine as our project management tools as well as bug tracking system at the very beginning. It's very easy to use although it is a little complex for new guys to set it up. Best of all, it's free and you can host it on your own server.
Used by IT team team to track all tickets for all products. All product defects, features and development tasks are entered in Redmine, categorized, and assigned to developers. All code releases are tracked along with the corresponding tickets within this system.