RedmineProjectSettings » History » Version 11

Mischa The Evil, 2009-06-07 03:56
Added screenshot

1 1 Jean-Philippe Lang
h1. Project Settings
2 1 Jean-Philippe Lang
3 10 Mischa The Evil
{{>toc}}
4 1 Jean-Philippe Lang
5 11 Mischa The Evil
!project-settings_information-tab.jpg!
6 11 Mischa The Evil
7 10 Mischa The Evil
h2. Information
8 1 Jean-Philippe Lang
9 10 Mischa The Evil
In this screen you can configure the basic (though important) settings for the selected project.
10 1 Jean-Philippe Lang
11 10 Mischa The Evil
h3. General settings
12 10 Mischa The Evil
13 10 Mischa The Evil
The following general settings are available:
14 1 Jean-Philippe Lang
* *Name*: project display name (must be unique).
15 1 Jean-Philippe Lang
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
19 7 Jean-Philippe Lang
* *Description*: description that appears on the project overview.
20 1 Jean-Philippe Lang
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.
22 1 Jean-Philippe Lang
23 10 Mischa The Evil
* *Homepage*: homepage-link that appears on the project overview.
24 1 Jean-Philippe Lang
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
h3. Trackers
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
41 1 Jean-Philippe Lang
h2. Modules
42 1 Jean-Philippe Lang
43 10 Mischa The Evil
This screen lets you choose the modules you want to use for the project. 
44 1 Jean-Philippe Lang
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.
46 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.
47 1 Jean-Philippe Lang
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
50 1 Jean-Philippe Lang
h2. Members
51 1 Jean-Philippe Lang
52 10 Mischa The Evil
This screen lets you define project members and their roles. A user can have only one role in a given project (but different roles on other projects).
53 1 Jean-Philippe Lang
54 10 Mischa The Evil
Note: starting from unscheduled version version#6 users can have multiple roles for a given project.
55 10 Mischa The Evil
56 1 Jean-Philippe Lang
h2. Versions
57 8 Mischa The Evil
58 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]].
59 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]].
60 9 Felix Dominguez
61 10 Mischa The Evil
The following properties are configurable for (each of the) versions:
62 10 Mischa The Evil
* *Name*: The text you want to be displayed to identify the version. _This field is required._
63 1 Jean-Philippe Lang
64 10 Mischa The Evil
* *Description*: A short description to describe the version. _This field is optional._
65 1 Jean-Philippe Lang
66 10 Mischa The Evil
* *Wiki Page*: The name of a wikipage assigned to the version. _This field is optional._
67 1 Jean-Philippe Lang
68 10 Mischa The Evil
* *Date*: The due date for the version to be completed. _This field is optional._
69 1 Jean-Philippe Lang
70 10 Mischa The Evil
71 1 Jean-Philippe Lang
h2. Issue categories
72 1 Jean-Philippe Lang
73 9 Felix Dominguez
Issue categories let you to organize issues. Categories can for example correspond to the different components of your project.
74 1 Jean-Philippe Lang
75 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.
76 10 Mischa The Evil
77 10 Mischa The Evil
The following properties are configurable for (each of the) issue categories:
78 10 Mischa The Evil
* *Name*: The text you want to be displayed to identify the issue category. _This field is required._
79 10 Mischa The Evil
80 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._
81 10 Mischa The Evil
82 3 Jean-Philippe Lang
h2. Wiki
83 4 Jean-Philippe Lang
84 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.
85 4 Jean-Philippe Lang
86 10 Mischa The Evil
Note: starting from unscheduled version version#6 you don't have to activate the main wikipage any longer.
87 10 Mischa The Evil
88 1 Jean-Philippe Lang
h2. Repository
89 3 Jean-Philippe Lang
90 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]].
91 10 Mischa The Evil
See [[RedmineRepositories|the following page]] for details about how to configure your repository in Redmine.
92 3 Jean-Philippe Lang
93 3 Jean-Philippe Lang
h2. Forums
94 4 Jean-Philippe Lang
95 10 Mischa The Evil
Each project can have one or more discussion forums. Each forum has the following properties:
96 10 Mischa The Evil
* *Name*: The text you want to be displayed to identify the discussion forum. _This field is required._
97 10 Mischa The Evil
98 10 Mischa The Evil
* *Description*: A short description to describe the subject of the specific forum. _This field is required._