Skip to main content
Projects are the top-level containers in Redmine. Each project has its own issues, wiki, forums, files, and members. Projects can be nested to create a hierarchy of subprojects.

Create a project

Set up a new project with its identifier, description, and visibility.

Manage members

Add users and groups with specific roles and permissions.

Enable modules

Turn individual features on or off per project.

Subprojects

Nest projects under a parent to share members and organise work.

​
Creating a project

1

Open the new project form

Click New project in the top navigation or go to Administration → Projects → New project.
2

Fill in project details

Provide a Name and optionally a Description and Homepage URL.
3

Set the identifier

The Identifier is a lowercase slug used in URLs (for example, my-project). It can only contain lowercase letters, digits, hyphens, and underscores and cannot be all digits. The identifier cannot be changed after the project is created.
4

Configure visibility

Choose Public to allow any user (including anonymous users if permitted) to view the project, or Private to restrict access to members only.
5

Set a parent project (optional)

Select a Parent project to make this a subproject. Members and settings can optionally be inherited from the parent.
6

Save

Click Create. You are redirected to the project settings page where you can configure modules and members.

​
Project statuses

StatusMeaning
ActiveThe project is open for work. Issues can be created and updated.
ClosedThe project is read-only. No new issues or changes are accepted.
ArchivedThe project is hidden from all listings. Data is preserved but inaccessible via the UI.

​
Project settings

Open Settings from within a project to configure the following sections.
  • Name — display name of the project
  • Description — shown on the project overview page
  • Homepage — external URL linked from the overview
  • Public / Private — project visibility
  • Inherit members — whether member roles are inherited from the parent project
  • Default issue query — pre-selected filter when opening the Issues list
  • Default assignee — fallback assignee when no assignee is set on a new issue
  • Default version — pre-selected target version for new issues
Enable or disable individual features for the project. Disabled modules are hidden from the project navigation.Available modules include: Issue tracking, Time tracking, News, Documents, Files, Wiki, Forums, Calendar, Gantt, Repository, and Activity.
Add users or groups to the project and assign one or more roles. Roles determine which actions each member can perform.Members can be added individually or by group. If Inherit members is enabled, members from the parent project are automatically included.
Define versions (milestones) for the project. Versions have a name, optional due date, and a status (open, locked, or closed). Issues can be targeted to a version.
Create categories for grouping issues within the project. Each category can have a default assignee.
Connect one or more version control repositories (Git, SVN, Mercurial, etc.) to the project. Changes in the repository can be linked to issues.
Choose which trackers are available for issues in this project. Trackers not selected here won’t appear in the new issue form.
Enable project-level custom fields that apply to issues in this project.

​
Enabling and disabling modules

1

Go to project settings

Open the project and click Settings in the sidebar.
2

Open the Modules tab

Click the Modules tab.
3

Toggle modules

Check or uncheck each module. Enabled modules appear as items in the project sidebar.
4

Save

Click Save to apply the changes.
Disabling a module hides it from the UI but does not delete its data. Re-enabling the module restores access to all existing content.

​
Project hierarchy (subprojects)

Redmine supports arbitrarily deep project trees. A project with a Parent project set is called a subproject.
  • Subprojects appear indented under their parent in the project list.
  • Issues can optionally include issues from all subprojects.
  • Versions, members, and custom fields can be shared or inherited from parent projects.
  • Setting Inherit members on a subproject copies the parent’s member roles into the subproject.
Use subprojects to represent components, teams, or phases of a larger project while keeping shared configuration at the parent level.

​
Project members

Members are users or groups associated with a project through one or more roles.
1

Open the Members tab

Go to Project → Settings → Members.
2

Add a member

Select a user or group from the search field and choose the role(s) to assign. Click Add.
3

Edit or remove a member

Click the edit icon next to a member to change their roles, or the delete icon to remove them from the project.
A user can have multiple roles in the same project. Their effective permissions are the union of all assigned roles.

​
Project overview

The project overview page (/projects/:identifier) shows a summary of the project:
  • Project description and homepage link
  • Latest news items
  • Active members
  • Latest issues
  • Current versions and their issue counts
You can customise the overview by editing the project description and ensuring the News and Issues modules are enabled.