RedmineProjectSettings » History » Version 18

Mischa The Evil, 2010-10-17 04:24
Enhanced Wiki-section.

1 1 Jean-Philippe Lang
h1. Project Settings
3 10 Mischa The Evil
4 1 Jean-Philippe Lang
5 10 Mischa The Evil
h2. Information
6 1 Jean-Philippe Lang
In this screen you can configure the basic (though important) settings for the selected project.
9 14 Jean-Philippe Lang
11 10 Mischa The Evil
h3. General settings
The following general settings are available:
14 1 Jean-Philippe Lang
* *Name*: project display name (must be unique).
15 10 Mischa The Evil
16 15 Tom Rochette
* *Subproject of*: lets you define a parent project to the project being created. 
(Pre version#6) The projects hierarchy is limited to 2 levels. A parent project cannot be itself a sub-project.
(Post version#6) Starting from version version#6, projects can be unlimitedly nested.
19 10 Mischa The Evil
20 7 Jean-Philippe Lang
* *Description*: description that appears on the project overview.
21 10 Mischa The Evil
22 1 Jean-Philippe Lang
* *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.
24 15 Tom Rochette
* *Homepage*: homepage-link that appears on the [[RedmineProjectOverview|project overview]].
25 1 Jean-Philippe Lang
26 15 Tom Rochette
* *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 [[RedmineRoles|role]].
27 1 Jean-Philippe Lang
28 15 Tom Rochette
If there are any [[RedmineCustomFields|custom fields]] of the type "Project" configured by the administrator, they'll show up behind the "Public"-setting noted above.
29 10 Mischa The Evil
h3. Trackers
32 15 Tom Rochette
Redmine lets you define which of the [[RedmineIssueTrackingSetup#Trackers|configured trackers]] (thus also their respective [[RedmineIssueTrackingSetup#Workflow|workflows]]) you are able to use within this specific project.
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.
h3. Custom fields
* *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.
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).
42 1 Jean-Philippe Lang
h2. Modules
44 10 Mischa The Evil
This screen lets you choose the modules you want to use for the project. 
45 1 Jean-Philippe Lang
46 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.
47 1 Jean-Philippe Lang
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.
49 10 Mischa The Evil
Additional modules can be added to the system using [[Plugins|Redmine plugins]]. Plugins can only be installed by the administrator.
51 1 Jean-Philippe Lang
h2. Members
53 13 Jean-Philippe Lang
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.
54 10 Mischa The Evil
55 1 Jean-Philippe Lang
h2. Versions
56 8 Mischa The Evil
57 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]].
You can also assign a wikipage to a version which will be added to the [[RedmineRoadmap|roadmap]] and the [[RedmineVersion|version overview]].
59 9 Felix Dominguez
60 10 Mischa The Evil
The following properties are configurable for (each of the) versions:
* *Name*: The text you want to be displayed to identify the version. _This field is required._
62 1 Jean-Philippe Lang
63 10 Mischa The Evil
* *Description*: A short description to describe the version. _This field is optional._
64 1 Jean-Philippe Lang
65 12 Jean-Philippe Lang
* *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
72 10 Mischa The Evil
* *Wiki Page*: The name of a wikipage assigned to the version. _This field is optional._
73 1 Jean-Philippe Lang
74 10 Mischa The Evil
* *Date*: The due date for the version to be completed. _This field is optional._
75 1 Jean-Philippe Lang
76 12 Jean-Philippe Lang
* *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.
85 1 Jean-Philippe Lang
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_.
86 10 Mischa The Evil
87 1 Jean-Philippe Lang
h2. Issue categories
89 9 Felix Dominguez
Issue categories let you to organize issues. Categories can for example correspond to the different components of your project.
90 1 Jean-Philippe Lang
91 15 Tom Rochette
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.
92 10 Mischa The Evil
The following properties are configurable for (each of the) issue categories:
* *Name*: The text you want to be displayed to identify the issue category. _This field is required._
95 1 Jean-Philippe Lang
96 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._
98 3 Jean-Philippe Lang
h2. Wiki
99 4 Jean-Philippe Lang
100 18 Mischa The Evil
Each project can have its own wiki. To activate it, give a name for the start page and click 'Save'. You are able to edit the chosen name for the start page here also.
101 1 Jean-Philippe Lang
102 18 Mischa The Evil
Note: starting from version#6 you don't have to explicitaly activate the projects wiki by setting a start page of the wiki any longer.
The project wiki will be automatically created with a default start page named '@Wiki@' when a project is created with a wiki module enabled or when the wiki module is enabled on an existing project.
104 10 Mischa The Evil
105 1 Jean-Philippe Lang
h2. Repository
106 3 Jean-Philippe Lang
107 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]].
See [[RedmineRepositories|the following page]] for details about how to configure your repository in Redmine.
109 3 Jean-Philippe Lang
h2. Forums
111 4 Jean-Philippe Lang
112 10 Mischa The Evil
Each project can have one or more discussion forums. 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._
116 16 Mischa The Evil
h2. Activities (time tracking)
119 17 Mischa The Evil