What is Redmine?
Who uses Redmine?
Why developers like Redmine?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Redmine in their tech stack.
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!
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. Redmine
- Multiple projects support
- Flexible role based access control
- Flexible issue tracking system
- Gantt chart and calendar
- News, documents & files management
- Feeds & email notifications
- Per project wiki
- Per project forums
- Time tracking
- Custom fields for issues, time-entries, projects and users
- SCM integration (SVN, CVS, Git, Mercurial, Bazaar and Darcs)
- Issue creation via email
- Multiple LDAP authentication support
- User self-registration support
- Multilanguage support
- Multiple databases support