It is being used in our group for project management including git repositories, files, documentation, etc. It is very suitable for our projects because one can have everything integrated into the same platform and we can work as a team with distinct levels of access for the different members in different projects.
Pros
It includes an internal Wiki to explain step by step how to do what we need.
A very complete project management and team collaboration platform.
Allows everyone to see all projects and tasks - no assigning to certain people.
Cons
Some of the dashboard features are tough to figure out.
Lacks an overview project main indicators dashboard.
It takes some training time to become an expert on using it.
Likelihood to Recommend
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.
We use Redmine across our organization between different departments. Initially, it was only used internally between sales, engineering, and project management teams. When we got more involved with certain customers and more back-and-forth was becoming cumbersome in emails, we moved the customers to start using the ticketing systems to alert us to any issues and keep track of their feature developments through transparency offered in Redmine tickets.
Major Use-Cases:
Priority assignments for developers .
Internal organization for resource management.
Communication between customer and project manager for status updates.
Quick reference for past issues.
Pros
Easy to upgrade and or change to your own particular use-cases.
Straightforward set-up and easy to create custom fields and workflows.
Communication between multiple teams.
Track multiple sprints through their chart views.
Keep a historical record of changes done to instances.
Cons
More flexibility for when fields are mandatory by type of user.
Create drag and drop updates in the list views for easy re-ordering of to-do-lists.
More ready-made analytics on time spent.
Likelihood to Recommend
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.
Our organization uses Redmine to track employees' work hours and make monthly reports. We have different projects with tasks there that are being created by a project manager. It's pretty simple to track your time and manage tasks, but Redmine is not very user-friendly and may cause different misunderstandings during work. But it is free to use, and that makes it useful for small organizations
Pros
Project management tools
Work hours control
Reporting tools
Free and open-source
Cons
Not very user-friendly
Contains bugs
Not easy to use
Likelihood to Recommend
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 used by the entire organization to manage projects and log time. Redmine provides one source for all resource management. We do have a PM who is in charge of Resource Management and she uses it more than anyone.
Pros
Redmine is particularly useful for seeing projects - their estimates, time worked and time remaining.
Redmine is an easy place for employees to log time against projects. This provides exports for payroll and for invoicing.
Redmine allows everyone to see all projects and tasks - no assigning to certain people.
Cons
The "more" features (log time, add a sub task, etc.) could be more prominent. This would make it easier for new users.
Some of the dashboard features are tough to figure out.
Likelihood to Recommend
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.
We've been using Redmine for at least 6 years as main project management solution in our company. As a free solution, it's a good task and time management system which allows you to be on the same page across the whole organization. Gantt charts and calendar are very useful. Notifications help you focus on the right things.
Pros
Easy to deploy
It's free
It's open-source
Highly customizable - it has plenty of plugins which can be integrated into the system
Integrated WIKI is very helpful
Cons
The UI is a little outdated
Sprint wise planning cant be done easily
Likelihood to Recommend
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.
Redmine is a fantastic tool. In our organization it began to serve as a tracking tool for the development bugs we had in different applications that we are doing, but the interesting thing was that little by little we realized that 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. We use an integration with Git by means of ssh, integration with Malyn Task Incubator for Eclipse and thus are able to have integration be continuous, since we integrate with Maven, Nexus, Jenkins, and SonarLint, and we are able to have a very optimal development in applications developed under Java in this case. Besides that the quality team can assign tasks to the corresponding department. It is one of the most complete tools that I have used. It also has the option of documenting since it has a built-in wiki, which makes it possible to have everything documented to perfection. Besides being developed in Ruby, it allows you to download the source code and customize your Redmine for your company.
Pros
Integration with several third-party tools
It has internal Wiki to document step by step what you want
Customizable from the source code
Connection via SSH
Cons
The interface is not very eye-catching, graphical view and user experience could use improvement
It takes training for like a month, since it has many tools and is difficult at first sight
Very little documentation on the internet
Likelihood to Recommend
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.