Skip to main content
Redmine is a flexible, open-source project management web application built with Ruby on Rails. Originally created by Jean-Philippe Lang in 2006, it has grown into a mature platform used by software teams, research groups, and organizations worldwide to plan, track, and collaborate on work of all kinds. Because Redmine is self-hosted and open-source, you control your data and can customize the tool to fit your team’s exact process — from the fields on an issue form to the status transitions allowed for each role.

​
Key features

Issue tracking

Create and manage bugs, features, tasks, and support requests. Assign priorities, due dates, categories, and custom fields. Link issues as related, duplicates, blocks, or subtasks.

Multi-project support

Manage many projects in one instance, each with its own members, modules, trackers, and settings. Projects can be nested to form a hierarchy.

Time tracking

Log time directly against issues or projects. Report on spent hours by user, project, or activity for billing and planning.

Wiki

Every project gets a collaborative wiki with version history, page linking, and text formatting. Use it for specs, runbooks, or meeting notes.

Forums

Per-project discussion boards (called Boards) keep conversations organized and searchable alongside the rest of your project data.

Repository browsing

Browse commits and source code from Git, Subversion, Mercurial, Bazaar, and other repositories directly in Redmine. Changesets are linked to issues automatically.

Gantt chart & calendar

Visualize issue due dates and version milestones on a Gantt chart or calendar view.

Plugins

Extend Redmine with a large ecosystem of community plugins, or build your own using the documented plugin API.

REST API

Integrate Redmine with CI/CD pipelines, chat tools, and other systems using the full-featured REST API.

​
Who Redmine is for

Redmine works well for teams that need a self-hosted, customizable alternative to commercial project management tools. It is especially popular with:
  • Software development teams that want issue tracking tightly integrated with source control
  • Open-source projects that need a free, community-friendly platform
  • Organizations with strict data-residency requirements that cannot use cloud-hosted tools
  • Teams with complex workflows that need fine-grained control over statuses, roles, and permissions

​
How Redmine is organized

At the top level, work is grouped into projects. Each project has its own set of enabled modules (issues, wiki, forums, time tracking, and so on), its own members with assigned roles, and its own configuration. Within a project, issues are the primary unit of work. Every issue belongs to a tracker (the issue type, such as Bug or Feature) and has a status (such as New, In Progress, or Closed). The transitions between statuses — who can move an issue from one status to another — are controlled by workflows that are configured per tracker and role. This model makes Redmine highly adaptable: a small team can run it with minimal configuration, while a large organization can define detailed workflows, custom fields, and role hierarchies.
This guide covers using Redmine as a regular user. If you are setting up or administering a Redmine instance, see the Administration section.

​
Where to go next

Quickstart

Log in for the first time, navigate the UI, join a project, create your first issue, and log time.

Core concepts

Understand the building blocks of Redmine: projects, issues, trackers, statuses, roles, workflows, and custom fields.