Redmine Reviews

It is a tool that does not is only for this use but with its great power of integration with other tools, we realized that in one solution we could cover many solutions. For instance, it is very well suited for git integration. Besides that, the quality team can assign tasks to the corresponding department. Maybe it is not very appropriate for very large and complex projects, where deeper monitoring of human resources, task deliverables, and deadlines is necessary.

For us specifically, we are a Ruby on Rails team, so customizing Redmine was easy to make it suit our needs. If we've needed different configurations for views, we developed it internally and updated our instance. I think Redmine does a great job in making known what feature requests are out there and which will be included in newer updates. The fact that we get to use it for free is a huge plus obviously. It does a great job with basic tracking of jobs that need to be done and assignment of teams who will need to be involved. It creates a great collection of comments, information, and feedback for future issues. We use Redmine also as a repository of historical changes per-client, so that we have a complete detailed record of all the requests made by the client for transparency on our control for them. We never deploy anything without approval from the client to production, and so we gain that information through updates in Redmine, and we have that record if we ever need to look back to it.

Redmine is free, so is perfectly suited for small developing companies to manage projects and employees' work hours. It's online and easy to start, and also can be used with every device. But it is a little laggy and complex, so if the company can afford something better, it might be a better fit.

Redmine is well suited if you are looking for a low-cost solution that is still robust and reliable. It is able to manage multiple projects and delegate appropriate access to members. It is also easy to use. Redmine can be less appropriate if you are looking for a system with a pretty interface and a good user experience. Although there are some themes available on the internet that can help you achieve that, Redmine does not have good usability.

In an organization managing multiple projects and having to monitor resource allocation, Redmine works very well. It's very similar to MS Project, but with an easier to use (I think) interface.

My opinion right now is that it's pretty out-dated solution. You can find a better solution which supports agile frameworks. But if you want it for free - yes, it's ok.

Setting aside the dated UI, Redmine is an excellent free, open-source tool for project management. It integrates with several code management tools and is easy to understand and use. It was built by developers, for developers, and thus development projects is where it really shines. That said, using it for general project management and overall release management isn't hard to accomplish.

Redmine is a great tool to tie teams together in small departments (note: different than small projects). It is an open source project, and it WILL require some learning curve to get it set up properly, and being able to configure it will be another, separate project altogether. But, coming from a Remedy environment, where you have an entire company within a company (nearly) to support and develop a Vendor-based product, I find Redmine to be an exciting alternative.

When you want to mount a continuous integration system Redmine is the perfect tool, since you can track quality perfectly. The interesting thing is that if it is well configured it is able to make quality when announcing a bug. It gives us the power to connect to IDE and display the code that has this bug and develop the solution and automatically save our code and make our commit in the IDE itself. We're able through other tools to upload our code and deploy automatically to test in a quality environment and then Redmine is responsible for sending a notification to both parts to indicate that the solution is already in pre-production and quality environment. Once this solution is approved by quality from Redmine, it triggers a trigger that makes the production pass automatically. The developer is something that simply is priceless, so this is very functional in large teams and very large applications where the level of development team is very large. It works perfectly to channel communication between developers and functional quality. Now if, on the other hand, you have a small project or a very small team of work this tool is not functional, since it really is wasting functionalities to have a complex tool for a development project that does not really require it.