RedmineProjectSettings » History » Version 13
Jean-Philippe Lang, 2010-01-09 14:53
groups as members
h1. Project Settings
|3||10||Mischa The Evil||
|5||11||Mischa The Evil||
|6||11||Mischa The Evil|
|7||10||Mischa The Evil||
|9||10||Mischa The Evil||
In this screen you can configure the basic (though important) settings for the selected project.
|11||10||Mischa The Evil||
h3. General settings
|12||10||Mischa The Evil|
|13||10||Mischa The Evil||
The following general settings are available:
* *Name*: project display name (must be unique).
|16||10||Mischa The Evil||
* *Subproject of*: lets you define the parent project. The projects hierarchy is limited to 2 levels. A parent project cannot be itself a sub-project.
|17||10||Mischa The Evil||
Note: starting from unscheduled version version#6 projects can be unlimitedly nested.
|18||10||Mischa The Evil|
* *Description*: description that appears on the project overview.
|21||10||Mischa The Evil||
* *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.
|23||10||Mischa The Evil||
* *Homepage*: homepage-link that appears on the project overview.
|25||10||Mischa The Evil||
* *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.
|26||10||Mischa The Evil|
|27||10||Mischa The Evil||
If there are any custom fields of the type "Project" configured by the administrator, they'll show up behind the "Public"-setting noted above.
|28||10||Mischa The Evil|
|29||10||Mischa The Evil||
|30||10||Mischa The Evil|
|31||10||Mischa The Evil||
Redmine lets you define which of the configured trackers (thus also their respective workflows) you are able to use within this specific project.
|32||10||Mischa The Evil|
|33||10||Mischa The Evil||
* *Trackers*: select the trackers that you want to use for issues of the project. Only the administrator can define new trackers.
|34||10||Mischa The Evil|
|35||10||Mischa The Evil||
h3. Custom fields
|36||10||Mischa The Evil|
|37||10||Mischa The Evil||
* *Custom fields*: select the custom fields (of the type @issues@) that you want to use for issues of the project. Only the administrator can define new custom fields.
|38||10||Mischa The Evil|
|39||10||Mischa The Evil||
Note that some of these custom fields can be only configured (e.g. unchecked) if the issue custom field is _not_ defined as a _global_ issue custom field (which can be done by the administrator by checking the "For all projects" checkbox in the custom field create/edit view).
|40||10||Mischa The Evil|
|43||10||Mischa The Evil||
This screen lets you choose the modules you want to use for the project.
|45||10||Mischa The Evil||
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.
|48||10||Mischa The Evil||
Additional modules can be added to the system using [[Plugins|Redmine plugins]]. Plugins can only be installed by the administrator.
|49||10||Mischa The Evil|
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 a given project.
|53||10||Mischa The Evil|
|55||8||Mischa The Evil|
|56||10||Mischa The Evil||
Projects versions allow you to track and plan changes. You can assign issues to versions and then view the list of assigned issues for each version on the [[RedmineRoadmap|roadmap]].
|57||10||Mischa The Evil||
You can also assign a wikipage to a version which will be added to the [[RedmineRoadmap|roadmap]] and the [[RedmineVersion|version overview]].
|59||10||Mischa The Evil||
The following properties are configurable for (each of the) versions:
|60||10||Mischa The Evil||
* *Name*: The text you want to be displayed to identify the version. _This field is required._
|62||10||Mischa The Evil||
* *Description*: A short description to describe the version. _This field is optional._
* *Status* (added in 0.9): 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
|71||10||Mischa The Evil||
* *Wiki Page*: The name of a wikipage assigned to the version. _This field is optional._
|73||10||Mischa The Evil||
* *Date*: The due date for the version to be completed. _This field is optional._
* *Sharing* (added in 0.9): 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 (same as above)
* all projects (can be set by admin users only)
Sharing a version of a private project with public projects will make its name visible to everyone.
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_.
|85||10||Mischa The Evil|
h2. Issue categories
Issue categories let you to organize issues. Categories can for example correspond to the different components of your project.
|90||10||Mischa The Evil||
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 for newly created issues.
|91||10||Mischa The Evil|
|92||10||Mischa The Evil||
The following properties are configurable for (each of the) issue categories:
|93||10||Mischa The Evil||
* *Name*: The text you want to be displayed to identify the issue category. _This field is required._
|94||10||Mischa The Evil|
|95||10||Mischa The Evil||
* *Assigned to*: The project member to who you want to auto-assign newly created issues in this category. _This field is optional._
|96||10||Mischa The Evil|
|99||10||Mischa The Evil||
Each project can have its own wiki. To activate it, give a name for the main page and click 'Save'. You are able to edit the chosen name for the main page here also.
|101||10||Mischa The Evil||
Note: starting from unscheduled version version#6 you don't have to activate the main wikipage any longer.
|102||10||Mischa The Evil|
|105||10||Mischa The Evil||
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 [[RedmineProjectActivity|Activity view]].
|106||10||Mischa The Evil||
See [[RedmineRepositories|the following page]] for details about how to configure your repository in Redmine.
|110||10||Mischa The Evil||
Each project can have one or more discussion forums. Each forum has the following properties:
|111||10||Mischa The Evil||
* *Name*: The text you want to be displayed to identify the discussion forum. _This field is required._
|112||10||Mischa The Evil|
|113||10||Mischa The Evil||
* *Description*: A short description to describe the subject of the specific forum. _This field is required._