RedmineProjectSettings » History » Version 27

« Previous - Version 27/39 (diff) - Next » - Current version
Bruce Svare, 2012-11-13 16:48


Project Settings

Information

In this screen you can configure the basic (though important) settings for the selected project.

Sceenshot of the information-tab of the project-settings

General settings

The following general settings are available:
  • Name: project display name. It must be unique.
  • Subproject of: lets you define a parent project to the project being created. Projects can be nested. You can only assign a project parent if you also have access to that parent.
  • Description: description that appears on the project overview.
  • Identifier: used by the application for various things (eg. in URLs). It must be unique. Once the project is created, this identifier cannot be modified. This autofills in when the project is created and a name is given.
  • Public: if checked, the project can be viewed by all the users, including those who are not members of the project. If unchecked, only the project members have access to it, according to their role. By default, all projects are private.
  • Project Number: the project number for easy storage and remembering.
  • Default Assignee: if there's only going to be one person working on the project, they can be listed here to have all issues automatically assigned to them.

Trackers

  • Trackers: select the trackers that you want to use for issues of the project. Only administrators can define new trackers.

Custom Fields

  • Custom fields: select the custom fields that you want to use for issues of the project. Only the administrator can define new custom fields.

Note that some of these custom fields can not be removed as they are set to global scope.

Modules

This screen lets you choose the modules you want to use for the project.

Disabling a module doesn't delete the associated data. It only prevents users from accessing it. After a module was disabled, it can be re-enabled with all its data.
You can for example disable 'Issue tracking' module for a single project. Existing issues are not deleted. You will be able to access them if you re-enable the module.

Core modules

Members

This screen lets you define project members and their roles. You can add a user or a group, with one or multiple role(s) in the project.

Versions

Projects versions allow you to track and plan changes. They are listed alphabetically. You can assign issues to versions and then view the list of assigned issues for each version on the roadmap.
You can also assign a wikipage to a version which will be added to the roadmap and the version overview.

Note: the roadmap menu-item shows up in the project-menu only when the issue tracking module is enabled for the project and at least one version is configured in the projects settings.

The following properties are configurable for each version:
  • Name: The text you want to be displayed to identify the version. This field is required.
  • Description: A short description to describe the version. This field is optional.
  • Status: the status lets you control how issues can be assigned to the version:
    • open: no restriction (default)
    • locked: can not assign new issues to the version
    • closed: can not assign new issues and can not reopen assigned issues. Appears as a closed issue on the roadmap.
  • Wiki Page: The name of a wikipage assigned to the version. This field is optional.
  • Date: The due date for the version to be completed. This field is optional.
  • Sharing: this option lets you share the version with other projects, so that issues from these other projects can be assigned to the shared versions. Each version can be shared with:
    • subprojects: all the descendant projects
    • projects in the project hierarchy: ancestors + descendants (needs versions management permission on the root project)
    • projects in the project tree: root project + all its descendants (needs versions management permission on the root project)
    • all projects (can be set by admin users only)
      ---------------------------------------------------------------------------------
      | None          | Subprojects   | Hierarchy     | Tree          | All projects  |
      |               |               |               |               |               |
      |      X     X  |      X     X  |      o     X  |      o     X  |      o     o  |
      |      |     |  |      |     |  |      |     |  |      |     |  |      |     |  |
      |    --X--   X  |    --X--   X  |    --o--   X  |    --o--   X  |    --o--   o  |
      |   /  |  \     |   /  |  \     |   /  |  \     |   /  |  \     |   /  |  \     |
      |  X   O   X    |  X   O   X    |  X   O   X    |  o   O   o    |  o   O   o    |
      |     / \       |     / \       |     / \       |     / \       |     / \       |
      |    X   X      |    o   o      |    o   o      |    o   o      |    o   o      |
      |   /           |   /           |   /           |   /           |   /           |
      |  X            |  o            |  o            |  o            |  o            |
      ---------------------------------------------------------------------------------
      
      O = project with the shared version
      o = projects that can assign issues to the shared version
      X = projects that can't assigne issues to the shared version
      
      Sharing a version of a private project with public projects will make its name visible to everyone.
  • ECO#: The ECO Number assigned to this version. This field is optional.

From the versions list, you can click on Close completed versions to automatically set the status of all the completed versions (due date reached and no open issues) to closed.

Issue categories

Issue categories let you to organize issues. Categories can for example correspond to the different components of your project.

You are able to configure your own set of issue categories for each individual project. It is also possible to auto-assign new issues to a specific user based on the chosen category of the newly created issues. Categories are listed alphabetically.

The following properties are configurable for each issue category:
  • Name: The text you want to be displayed to identify the issue category. This field is required.
  • Assigned to: The project member to who you want to auto-assign newly created issues in this category. This field is optional.

Wiki

Each project can have its own wiki. Enable the module on the desired project to activate it.

  • Start page: This page is used as the start page for the wiki in both the project menu wiki link as well as in the start page link in the wiki sidebar (default: 'Wiki'). This field is required.

Repository

A SCM repository can be associated with each project. Once the repository is configured, you can browse it and view the changesets. The changesets also appear in the Activity view.
See Repositories for details about how to configure your repository in Redmine.

Forums

Each project can have one or more discussion forums. The forums can be arranged in any order. Each forum has the following properties:
  • Name: The text you want to be displayed to identify the discussion forum. This field is required.
  • Description: A short description to describe the subject of the specific forum. This field is required.

Activities (time tracking)

TODO

project-settings_information-tab.jpg - Sceenshot of the information-tab of the project-settings (21.8 KB) Mischa The Evil, 2009-06-07 03:51