Project

General

Profile

RusRedmineProjectSettings » History » Version 2

Ruslan Khasanov, 2013-03-16 19:20

1 2 Ruslan Khasanov
[[RusGuide|Руководство]]->[[RusUser_Guide|Руководство пользователя]]
2
3
Оригинал: [[RedmineProjectSettings|Project settings v.30]]
4
5
h1. Настройки проекта
6
7
{{>toc}}
8
9
h2. Information
10
11
In this screen you can configure the basic (though important) settings for the selected project.
12
13
!project-settings_information-tab.jpg!
14
15
h3. General settings
16
17
The following general settings are available:
18
* *Name*: project display name (must be unique).
19
20
* *Subproject of*: lets you define a parent project to the project being created. Projects can be unlimitedly nested.
21
22
* *Description*: description that appears on the project overview.
23
24
* *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.
25
26
* *Homepage*: homepage-link that appears on the [[RedmineProjectOverview|project overview]].
27
28
* *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]].
29
30
If there are any [[RedmineCustomFields#Fields-for-Projects|projects custom fields]] configured by the administrator, they'll show up behind the "Public"-setting noted above.
31
32
h3. Trackers
33
34
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.
35
36
* *Trackers*: select the trackers that you want to use for issues of the project. Only the administrator can define new trackers.
37
38
h3. Custom fields
39
40
* *Custom fields*: select the [[RedmineCustomFields#Fields-for-Issues|issues custom fields]] that you want to use for issues of the project. Only the administrator can define new [[RedmineCustomFields|custom fields]].
41
42
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).
43
44
h2. Modules
45
46
This screen lets you choose the modules you want to use for the project.
47
48
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.
49
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.
50
51
h3. Core modules
52
53
* Issue tracking: provides [[RedmineIssues|Issue tracking]] feature, including [[RedmineProjectSettings#Issue-categories|issue categories]], [[RedmineProjectSettings#Versions|versions]], the [[RedmineRoadmap|Roadmap]] and [[RedmineVersion|version overviews]]
54
* Time tracking: provides [[RedmineTimeTracking|Time tracking]] feature
55
* News: provides [[RedmineNews|News]] feature
56
* Documents: provides [[RedmineDocuments|Documents]] feature
57
* Files: provides [[RedmineFiles|Files]] feature
58
* Wiki: provides [[RedmineWikis|Wiki]] feature
59
* Repository: provides [[RedmineRepository|Repository]] feature
60
* Boards: provides [[RedmineForums|Forum]] feature
61
* Calendar: provides [[RedmineCalendar|Calendar]] feature
62
* Gantt: provides [[RedmineGantt|Gantt]] feature
63
64
Additional modules can be added to the system using [[Plugins|Redmine plugins]]. Plugins can only be installed by the administrator.
65
66
h2. Members
67
68
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.
69
70
h2. Versions
71
72
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]].
73
You can also assign a wikipage to a version which will be added to the [[RedmineRoadmap|roadmap]] and the [[RedmineVersion|version overview]].
74
75
_Note: the [[RedmineRoadmap|roadmap]] menu-item shows up in the project-menu only when the issue tracking [[RedmineProjectSettings#Core-modules|module]] is enabled for the project and at least one [[RedmineProjectSettings#Versions|version]] is configured in the [[RedmineProjectSettings|projects settings]]._
76
77
The following properties are configurable for (each of the) versions:
78
* *Name*: The text you want to be displayed to identify the version. _This field is required._
79
80
* *Description*: A short description to describe the version. _This field is optional._
81
82
* *Status*: the status lets you control how issues can be assigned to the version:
83
84
  * open: no restriction (default)
85
  * locked: can not assign new issues to the version
86
  * closed: can not assign new issues and can not reopen assigned issues
87
88
* *Wiki Page*: The name of a wikipage assigned to the version. _This field is optional._
89
90
* *Date*: The due date for the version to be completed. _This field is optional._
91
92
* *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:
93
94
  * subprojects: all the descendant projects
95
  * projects in the project hierarchy: ancestors + descendants (needs versions management permission on the root project)
96
  * projects in the project tree: root project + all its descendants (same as above)
97
  * all projects (can be set by admin users only)
98
99
<pre>
100
---------------------------------------------------------------------------------
101
| None          | Subprojects   | Hierarchy     | Tree          | All projects  |
102
|               |               |               |               |               |
103
|      X     X  |      X     X  |      o     X  |      o     X  |      o     o  |
104
|      |     |  |      |     |  |      |     |  |      |     |  |      |     |  |
105
|    --X--   X  |    --X--   X  |    --o--   X  |    --o--   X  |    --o--   o  |
106
|   /  |  \     |   /  |  \     |   /  |  \     |   /  |  \     |   /  |  \     |
107
|  X   O   X    |  X   O   X    |  X   O   X    |  o   O   o    |  o   O   o    |
108
|     / \       |     / \       |     / \       |     / \       |     / \       |
109
|    X   X      |    o   o      |    o   o      |    o   o      |    o   o      |
110
|   /           |   /           |   /           |   /           |   /           |
111
|  X            |  o            |  o            |  o            |  o            |
112
---------------------------------------------------------------------------------
113
114
O = project with the shared version
115
o = projects that can assign issues to the shared version
116
X = projects that can't assigne issues to the shared version
117
</pre> Sharing a version of a private project with public projects will make its name visible to everyone.
118
119
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_.
120
121
h2. Issue categories
122
123
Issue categories let you to organize issues. Categories can for example correspond to the different components of your project.
124
125
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.
126
127
The following properties are configurable for (each of the) issue categories:
128
* *Name*: The text you want to be displayed to identify the issue category. _This field is required._
129
130
* *Assigned to*: The project member to who you want to auto-assign newly created issues in this category. _This field is optional._
131
132
h2. Wiki
133
134
Each project can have its own wiki. Enable the [[RedmineProjectSettings#Modules|module]] on the desired project to activate it.
135
136
* *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 [[RedmineWikis#Sidebar|wiki sidebar]] (default: 'Wiki'). _This field is required._
137
138
h2. Repository
139
140
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]].
141
See [[RedmineRepositories|the following page]] for details about how to configure your repository in Redmine.
142
143
h2. Forums
144
145
Each project can have one or more discussion forums. Each forum has the following properties:
146
* *Name*: The text you want to be displayed to identify the discussion forum. _This field is required._
147
148
* *Description*: A short description to describe the subject of the specific forum. _This field is required._
149
150
h2. Activities (time tracking)
151
152
TODO