RusRedmineProjectSettings » History » Version 2

Ruslan Khasanov, 2013-03-16 19:20

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