diff --git a/config/help.yml b/config/help.yml
index b02a06fb..69c45db7 100644
--- a/config/help.yml
+++ b/config/help.yml
@@ -26,38 +26,49 @@ pages:
# administration
admin:
index: ch01.html
- mail_options: ch01s08.html
- info: ch01s09.html
+ mail_options: ch01s09.html
+ info: ch01s11.html
users:
- index: ch01s01.html
- roles:
index: ch01s02.html
- workflow: ch01s06.html
- trackers:
+ roles:
index: ch01s03.html
+ workflow: ch01s07.html
+ trackers:
+ index: ch01s04.html
issue_statuses:
- index: ch01s05.html
+ index: ch01s06.html
# projects
projects:
index: ch02.html
- add: ch02s08.html
+ add: ch01s01.html
show: ch02s01.html
- add_document: ch02s06.html
- list_documents: ch02s06.html
- add_issue: ch02s02.html
- list_issues: ch02s02.html
- add_news: ch02s05.html
- list_news: ch02s05.html
- add_file: ch02s07.html
- list_files: ch02s07.html
- changelog: ch02s04.html
+ gantt: ch02s02.html
+ calendar: ch02s02.html
+ add_document: ch02s07.html
+ list_documents: ch02s07.html
+ add_issue: ch02s03.html
+ list_issues: ch02s03.html
+ add_news: ch02s06.html
+ list_news: ch02s06.html
+ add_file: ch02s08.html
+ list_files: ch02s08.html
+ changelog: ch02s05.html
issues:
- index: ch02s02.html
+ index: ch02s03.html
documents:
- index: ch02s06.html
+ index: ch02s07.html
news:
- index: ch02s05.html
+ index: ch02s06.html
versions:
- index: ch02s08.html
+ index: ch02s09.html
reports:
- index: ch02s03.html
\ No newline at end of file
+ index: ch02s04.html
+ # accounts
+ my:
+ index: ch03.html
+ account: ch03s01.html
+ page: ch03s02.html
+ account:
+ index: ch03.html
+ lost_password: ch03s03.html
+ register: ch03s04.html
\ No newline at end of file
diff --git a/doc/CHANGELOG b/doc/CHANGELOG
index 204453b5..7dc2b923 100644
--- a/doc/CHANGELOG
+++ b/doc/CHANGELOG
@@ -1,11 +1,11 @@
== redMine changelog
redMine - project management software
-Copyright (C) 2006 Jean-Philippe Lang
-http://redmine.org/
+Copyright (C) 2006-2007 Jean-Philippe Lang
+http://redmine.rubyforge.org/
-== xx/xx/2006 v0.x.x
+== xx/xx/2006 v0.4.0
* simple SVN browser added (just needs svn binaries in PATH)
* comments can now be added on news
@@ -20,7 +20,8 @@ http://redmine.org/
* gantt chart added (exportable to pdf)
* single/multiple issues pdf export added
* issues reports improvements
-* multiple file upload for issues attachments
+* multiple file upload for issues, documents and files
+* option to set maximum size of uploaded files
* textile formating of issue and news descritions (RedCloth required)
* integration of DotClear jstoolbar for textile formatting
* calendar date picker for date fields (LGPL DHTML Calendar http://sourceforge.net/projects/jscalendar)
@@ -32,10 +33,14 @@ http://redmine.org/
* csv output encoded to ISO-8859-1
* user custom field displayed on account/show
* default configuration improved (default roles, trackers, status, permissions and workflows)
+* language for default configuration data can now be chosen when running 'load_default_data' task
* javascript added on custom field form to show/hide fields according to the format of custom field
* fixed: custom fields not in csv exports
* fixed: project settings now displayed according to user's permissions
* fixed: application error when no version is selected on projects/add_file
+* fixed: public actions not authorized for members of non public projects
+* fixed: non public projects were shown on welcome screen even if current user is not a member
+
== 10/08/2006 v0.3.0
diff --git a/doc/INSTALL b/doc/INSTALL
index 9e29b6dd..a7736749 100644
--- a/doc/INSTALL
+++ b/doc/INSTALL
@@ -1,20 +1,18 @@
== redMine installation
redMine - project management software
-Copyright (C) 2006 Jean-Philippe Lang
-http://redmine.org/
+Copyright (C) 2006-2007 Jean-Philippe Lang
+http://redmine.rubyforge.org/
== Requirements
* Ruby on Rails 1.1
* Iconv
-* a database (see compatibility below)
-* (recommended) Apache/Lighttpd with FCGI support
+* A database (see compatibility below)
Optional:
* RedCloth (for textile formatting)
-* Net::LDAP for Ruby (for LDAP authentication)
Supported databases:
* MySQL (tested with MySQL 5)
@@ -40,14 +38,15 @@ Next releases (0.3.0+) will be provided with upgrade support.
3. Configure database parameters in config/database.yml
for "production" environment (default database is MySQL)
-4. Create the database structure. Under application main directory:
+4. Create the database structure. Under the application main directory:
rake migrate RAILS_ENV="production"
- It will create tables and default configuration data
+ It will create tables and an administrator account.
5. Insert default configuration data in database:
rake load_default_data RAILS_ENV="production"
- This step is optional, as you can define your own configuration
- (roles, trackers, statuses, workflows, enumerations) from sratch
+ It will load default roles, trackers, statuses, workflows and enumerations.
+ This step is optional (but recommended), as you can define your
+ own configuration from sratch.
6. Test the installation by running WEBrick web server:
ruby script/server -e production
diff --git a/doc/README b/doc/README
index 42a0bc18..b839c85b 100644
--- a/doc/README
+++ b/doc/README
@@ -1,8 +1,8 @@
== redMine
redMine - project management software
-Copyright (C) 2006 Jean-Philippe Lang
-http://redmine.org/
+Copyright (C) 2006-2007 Jean-Philippe Lang
+http://redmine.rubyforge.org/
== License
@@ -25,16 +25,19 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
redMine is a project management software written using Ruby on Rails.
-* multiple users/projects
-* fully customizable role based access control
-* issue tracking system
-* fully customizable workflow
-* documents/files repository
-* email notifications
-* custom fields for projects, users and issues
-* multilanguage support
-* multiple LDAP authentication support
-* user self-registration support
+* Multiple users/multiple projects
+* Fully customizable role based access control
+* Issue tracking system
+* Fully customizable workflow
+* Documents/files repository
+* News management
+* SVN browser and diff viewer
+* Email notifications
+* Custom fields for projects, users and issues
+* Multiple LDAP authentication support
+* User self-registration support
+* Multilanguage support (english, french, german, spanish)
+* Multiple databases support: MySQL, PostgreSQL, Oracle, SQL Server, SQLite
== User documentation
@@ -54,5 +57,5 @@ may not be provided for these versions.
* Jean-Francois Boutier (spanish translation)
* Andreas Viklund (open source XHTML layout, http://andreasviklund.com/)
-* Karim Trott (german translation)
+* Karim Trott (german translation and english online help translation)
diff --git a/doc/docbook/en/images/arrow_bw.png b/doc/docbook/en/images/arrow_bw.png
new file mode 100644
index 00000000..c50fbce8
Binary files /dev/null and b/doc/docbook/en/images/arrow_bw.png differ
diff --git a/doc/docbook/en/images/arrow_from.png b/doc/docbook/en/images/arrow_from.png
new file mode 100644
index 00000000..f1e1b6c3
Binary files /dev/null and b/doc/docbook/en/images/arrow_from.png differ
diff --git a/doc/docbook/en/images/arrow_to.png b/doc/docbook/en/images/arrow_to.png
new file mode 100644
index 00000000..faef20c7
Binary files /dev/null and b/doc/docbook/en/images/arrow_to.png differ
diff --git a/doc/docbook/en/images/gantt.png b/doc/docbook/en/images/gantt.png
new file mode 100644
index 00000000..65c33d68
Binary files /dev/null and b/doc/docbook/en/images/gantt.png differ
diff --git a/doc/docbook/en/images/issues_list.png b/doc/docbook/en/images/issues_list.png
new file mode 100644
index 00000000..520de14b
Binary files /dev/null and b/doc/docbook/en/images/issues_list.png differ
diff --git a/doc/docbook/en/images/locked.png b/doc/docbook/en/images/locked.png
new file mode 100644
index 00000000..5199dfe2
Binary files /dev/null and b/doc/docbook/en/images/locked.png differ
diff --git a/doc/docbook/en/images/roles_edit.png b/doc/docbook/en/images/roles_edit.png
new file mode 100644
index 00000000..a1ed2755
Binary files /dev/null and b/doc/docbook/en/images/roles_edit.png differ
diff --git a/doc/docbook/en/images/user_new.png b/doc/docbook/en/images/user_new.png
new file mode 100644
index 00000000..0c220257
Binary files /dev/null and b/doc/docbook/en/images/user_new.png differ
diff --git a/doc/docbook/en/images/users_list.png b/doc/docbook/en/images/users_list.png
new file mode 100644
index 00000000..74d9c9a5
Binary files /dev/null and b/doc/docbook/en/images/users_list.png differ
diff --git a/doc/docbook/en/images/workflow.png b/doc/docbook/en/images/workflow.png
new file mode 100644
index 00000000..04e79d61
Binary files /dev/null and b/doc/docbook/en/images/workflow.png differ
diff --git a/doc/docbook/en/redmine-userdoc-en.xml b/doc/docbook/en/redmine-userdoc-en.xml
index c290bb85..6b7a1c85 100644
--- a/doc/docbook/en/redmine-userdoc-en.xml
+++ b/doc/docbook/en/redmine-userdoc-en.xml
@@ -1,429 +1,716 @@
-
+
- RedMine Documentation
+ Documentation
+
- Administration
-
- Users
- These screens allow you to manage the application users.
-
- Users’ List
-
-
- Users’ List
-
-
-
-
-
-
- The Lock/Unlock buttons allow you to lock/unlock the user accounts.
- A user having a locked account cannot log in and access the application.
-
-
- User Creation or Modification
- In modification mode, please leave the Password field blank in order to keep the user’s password unchanged.
- A user designated as administrator has unrestricted access to the application and to all projects.
-
-
-
- Administrator
- : designate the user as the administrator of the application.
-
-
-
-
- E-mail notifications
- : activate or de-activate automatic e-mail notifications for this user
-
-
-
-
- Locked
- : de-activates the user’s account
-
-
-
-
-
-
-
- Roles and Permissions
- Roles organize the permissions of various members of a project. Each member of a project has a one Role in a project. A user can have different roles in different projects.
- On the new or edit Role screen, check off the actions authorized for the Role.
-
-
- Trackers
- Trackers allow the sorting of Issues and can define specific workflows.
-
-
- Customized fields
- Customized fields allow you to add additional information in Projects, Issues or Users. A customized field can be of one the following types:
-
-
-
- Integer
- : positive or negative number
-
-
-
-
- String
- : a string of characters - one single line of input.
-
-
-
-
- Text
- : a string of characters with multiple lines of input. Differs from String Format by providing multiple lines of input instead of a single line.
-
-
-
-
- Date
- : date
-
-
-
-
- Boolean
- : true or false (check if necessary)
-
-
-
-
- List
- : value to select from a predefined list (aka: scroll list or select box)
-
-
-
- Validation elements can be defined:
-
-
-
- Required
- : A required field must have input in the forms
-
-
-
-
- For all the projects
- : field automatically associated to all of the projects
-
-
-
-
- Min - max length
- : minimum and maximum length for the input fields (0 means that there is no restriction)
-
-
-
-
- Regular Expression
- : regular expressions may provide validation of the input value
-
- Examples:
-
- ^\[A-Z]{4}\d+$
- : 4 capital letters followed by one or several digits
-
-
- ^[^0-9]*$
- : characters only - no digits
-
-
-
-
- Possible values
- : possible values for the fields of "List" type. Values are separated by the character |
-
-
-
-
-
- Fields for Projects
-
-
-
-
- Required
- : required field
-
-
-
-
-
-
- Fields for Issues
-
-
-
-
- For all projects
- : field automatically associated to all project Issues
-
- If this option is not activated, each project could choose whether or not to use the field for its Issues (please see the project configuration).
-
-
-
-
-
- Field for Users
-
-
-
-
- Required
- : required field
-
-
-
-
-
-
-
- Issue status
- These screens allow you to define the different possible Issue statuses.
-
-
-
- Closed
- : indicates Issue is considered as closed
-
-
-
-
- Default
- : status applied by default to new Issue requests (only one status can be Default status)
-
-
-
-
- Color
- : HTML color code (6 characters) representing the displayed status
-
-
-
-
-
-
- Workflow
- The workflow allows to define changes the various project members are allowed to make on the Issues, according to their type.
- Select the role and the tracker for which you want to modify the workflow, then click Edit. The screen allows you then to modify the authorized change, for the chosen role and tracker. The Current Status options indicate the initial request status. The "New Statuses allowed" columns stand for the authorized status to apply.
-
- Note: In order for a particular Role to change an Issue status, the authorization must be given to it explicitly, regardless of the workflow configuration.
-
-
-
- Example of a workflow configuration
-
-
-
-
-
-
- In the above example, Bug type Issue requests with a New status could be given an Assigned or Resolved status by the Developer role. Those with an Assigned status could get a Resolved status. The status of all the other Bug type requests cannot be modified by the Developer.
-
-
- Enumerations
- The value lists used by the application can be customized (for example, setting Issue priorities). This screen allows you to define the possible values for each of the following lists:
-
-
- Issue Priorities
-
-
- Document Categories
-
-
-
-
-
- E-mail notifications
- This screen allows you to select the actions that will generate an e-mail notification for project members.
- Note: E-mail sending must be activated in the application configuration if you want to make any notifications.
-
-
- Authentication
- By default, redMine refers to its own database to authenticate users, by a specific password.
- If you already have one or several external user references (like LDAP), you can make them known in order to be used for authentication on redMine. This allows users to access redMine with their usual user names and passwords.
- For each known reference, you can specify if the accounts can be created on the fly on redMine. If needed, the user accounts will be created automatically during the user’s signing in (without any specific rights on the projects), according to information available in the reference. Otherwise, the administrator must have previously created the user account on redMine.
-
-
- LDAP statement
-
-
-
-
- Name
- : reference display name
-
-
-
-
- Host
- : LDAP server host name
-
-
-
-
- Port
- : connection port to the LDAP server
-
-
-
-
- Account
- : DN of the connection account to LDAP (please leave it blank if the directory authorizes anonymous read access)
-
-
-
-
- Password
- : password of the connection account
-
-
-
-
- Base DN
- : Basic DN used for user search in the directory
-
-
-
-
- LDAP screen
- : User search screen in the directory (optional)
-
-
-
-
- LDAP features
- :
-
-
-
-
- Identifier
- : LDAP feature name used as user identifier (e.g.: uid)
-
-
-
-
- First name
- : LDAP feature name including the user’s first name (ex: givenName)
-
-
-
-
- Last name
- : LDAP feature name including the user’s last name (ex: familyName)
-
-
-
-
- E-mail
- : LDAP feature name including the user’s e-mail address (ex: mail)
-
-
-
-
-
-
- The features"
- First name
- ", "
- Last name
- " and "
- E-mail
- " are not used except when the accounts are created on the fly.
-
-
-
-
- Information
- Displays application and environment information.
-
+ Administration
+
+
+ Projects
+
+ These screens allow you to manage projects.
+
+
+
+ Users
+
+ These screens allow you to manage the application users.
+
+
+ Users’ List
+
+
+
+
+ Users’ List
+
+
+
+
+
+
+
+
+ Accounts status:
+
+
+
+ This icon
+
+
+
+ means that the account is locked. A user
+ having a locked account cannot log in and access the
+ application.
+
+
+
+ This icon
+
+
+
+ means that the user hasn't yet actived his
+ account.
+
+
+
+ The Lock/Unlock buttons allow you to lock/unlock the user
+ accounts.
+
+
+
+
+
+ User Creation or Modification
+
+ In modification mode, please leave the Password field blank in
+ order to keep the user’s password unchanged.
+
+ A user designated as administrator has unrestricted access to
+ the application and to all projects.
+
+
+
+ Administrator :
+ designate the user as the administrator of the application.
+
+
+
+ E-mail notifications :
+ activate or de-activate automatic e-mail notifications for this
+ user
+
+
+
+ Locked : de-activates
+ the user’s account
+
+
+
+
+
+
+
+
+ Roles and Permissions
+
+ Roles organize the permissions of various members of a project.
+ Each member of a project has a one Role in a project. A user can have
+ different roles in different projects.
+
+ On the new or edit Role screen, check off the actions authorized
+ for the Role.
+
+
+
+ Trackers
+
+ Trackers allow the sorting of Issues and can define specific
+ workflows.
+
+
+
+ Custom fields
+
+ Custom fields allow you to add additional information in Projects,
+ Issues or Users. A custom field can be of one the following
+ types:
+
+
+
+ Integer : positive or
+ negative number
+
+
+
+ String : a string of
+ characters - one single line of input.
+
+
+
+ Text : a string of
+ characters with multiple lines of input. Differs from String Format
+ by providing multiple lines of input instead of a single
+ line.
+
+
+
+ Date : date
+
+
+
+ Boolean : true or false
+ (check if necessary)
+
+
+
+ List : value to select
+ from a predefined list (aka: scroll list or select box)
+
+
+
+ Validation elements can be defined:
+
+
+
+ Required : A required
+ field must have input in the forms
+
+
+
+ For all the projects :
+ field automatically associated to all of the projects
+
+
+
+ Min - max length :
+ minimum and maximum length for the input fields (0 means that there
+ is no restriction)
+
+
+
+ Regular Expression :
+ regular expressions may provide validation of the input value
+
+ Examples:
+
+ ^\[A-Z]{4}\d+$ : 4 capital letters followed by
+ one or several digits
+
+ ^[^0-9]*$ : characters only - no digits
+
+
+
+ Possible values :
+ possible values for the fields of "List" type. Values are separated
+ by the character |
+
+
+
+
+
+
+ Fields for Projects
+
+
+
+
+
+ Required : required
+ field
+
+
+
+
+
+
+
+ Fields for Issues
+
+
+
+
+
+ For all projects :
+ field automatically associated to all project Issues
+
+ If this option is not activated, each project could choose
+ whether or not to use the field for its Issues (please see the
+ project configuration).
+
+
+
+
+
+
+
+ Field for Users
+
+
+
+
+
+ Required : required
+ field
+
+
+
+
+
+
+
+
+ Issue status
+
+ These screens allow you to define the different possible Issue
+ statuses.
+
+
+
+ Closed : indicates Issue
+ is considered as closed
+
+
+
+ Default : status applied
+ by default to new Issue requests (only one status can be Default
+ status)
+
+
+
+ Color : HTML color code
+ (6 characters) representing the displayed status
+
+
+
+
+
+
+
+ Workflow
+
+ The workflow allows to define changes the various project members
+ are allowed to make on the Issues, according to their type.
+
+ Select the role and the tracker for which you want to modify the
+ workflow, then click Edit. The screen allows you then to modify the
+ authorized change, for the chosen role and tracker. The Current Status
+ options indicate the initial request status. The "New Statuses allowed"
+ columns stand for the authorized status to apply.
+
+ Note: In order for a particular Role to change an Issue
+ status, the authorization must be given to it explicitly, regardless of
+ the workflow configuration.
+
+
+
+
+ Example of a workflow configuration
+
+
+
+
+
+
+
+
+ In the above example, Bug type Issue requests with a New status
+ could be given an Assigned or Resolved status by the Developer role.
+ Those with an Assigned status could get a Resolved status. The status of
+ all the other Bug type requests cannot be modified by the
+ Developer.
+
+
+
+ Enumerations
+
+ The value lists used by the application can be customized (for
+ example, setting Issue priorities). This screen allows you to define the
+ possible values for each of the following lists:
+
+
+
+ Issue Priorities
+
+
+
+ Document Categories
+
+
+
+
+
+
+
+ E-mail notifications
+
+ This screen allows you to select the actions that will generate an
+ e-mail notification for project members.
+
+ Note: E-mail sending must be activated in the application
+ configuration if you want to make any notifications.
+
+
+
+ Authentication
+
+ By default, redMine refers to its own database to authenticate
+ users, by a specific password.
+
+ If you already have one or several external user references (like
+ LDAP), you can make them known in order to be used for authentication on
+ redMine. This allows users to access redMine with their usual user names
+ and passwords.
+
+ For each known reference, you can specify if the accounts can be
+ created on the fly on redMine. If needed, the user accounts will be
+ created automatically during the user’s signing in (without any specific
+ rights on the projects), according to information available in the
+ reference. Otherwise, the administrator must have previously created the
+ user account on redMine.
+
+
+
+
+ LDAP statement
+
+
+
+
+
+ Name : reference
+ display name
+
+
+
+ Host : LDAP server host
+ name
+
+
+
+ Port : connection port
+ to the LDAP server
+
+
+
+ Account : DN of the
+ connection account to LDAP (please leave it blank if the directory
+ authorizes anonymous read access)
+
+
+
+ Password : password of
+ the connection account
+
+
+
+ Base DN : Basic DN used
+ for user search in the directory
+
+
+
+ LDAP screen : User
+ search screen in the directory (optional)
+
+
+
+ LDAP features :
+
+
+
+ Identifier : LDAP
+ feature name used as user identifier (e.g.: uid)
+
+
+
+ First name : LDAP
+ feature name including the user’s first name (ex:
+ givenName)
+
+
+
+ Last name : LDAP
+ feature name including the user’s last name (ex:
+ familyName)
+
+
+
+ E-mail : LDAP
+ feature name including the user’s e-mail address (ex:
+ mail)
+
+
+
+
+
+ The features" First name ",
+ " Last name " and " E-mail " are not used except when the
+ accounts are created on the fly.
+
+
+
+
+ Information
+
+ Displays application and environment information.
+
+
- Projects
-
- Project preview
- The preview presents the general project information, its main members, the latest announcements, as well as an synthesis of Issue requests open by tracker.
-
-
-
- Issue management
-
-
- Issue list
- By default, the entire list of the project open Issues are displayed. Various screens allow you to select the Issues to be displayed. If the project has sub-projects, you have the possibility to display the sub-project's Issues as well (not displayed by default).
- Once applied, a screen is valid during the entire session. You can re-define it or delete it by clicking Cancel.
-
-
- Request list
-
-
-
-
-
-
-
-
-
-
- Reports
- This screen presents the number of Issues and Issue status synthesis according to various criteria (tracker, priority, category). Direct links allow for access to the detailed Issue list for each criterion.
-
-
- Change log
- This page presents the entire list of the resolved Issues for each version of the project. Certain types of Issues can be excluded from this display.
-
-
- News
- Allows you to inform users on project activity.
-
-
- Documents
- Documents are grouped by categories (see Value Lists). A document can contain several files (for example: revisions or successive versions).
-
-
- Files
- This module allows you to display various folders (sources, binaires, ...) for each version of the application.
-
-
- Settings
-
-
- Project features
-
-
-
-
- Public
- : if it’s a public project, it can be viewed (request consultation, documents consultation, ...) for all the users, including those who are not project members. If it’s not a public project, only the project members have access to it, according to their role.
-
-
-
-
- Customized fields
- : Select the customized fields that you want to use. Only the administrator can define new customized fields.
-
-
-
-
-
-
- Members
- This screen allows you to define the project members as well as their corresponding roles. A user can have only one role in a given project. The role of a member determines the permissions they have in a project.
-
-
- Versions
- Versions allow you to follow the changes made during all the project. For instance, at the close of an Issue, you can indicate which version takes it into account. You can display the various versions of the application (see Files).
-
-
- Request categories
- Issue categories allow you to organize Issues. Categories can correspond to different project modules.
-
-
+ Projects
+
+
+ Project overview
+
+ The overview presents the general project information, its main
+ members, the latest announcements, as well as an synthesis of Issue
+ requests open by tracker.
+
+
+
+
+
+ Planning
+
+
+
+
+ Project calendar
+
+ Project calendar shows the tasks that begin or end during the
+ selected month (current month by default). An issue will be displayed
+ as a task if its start date and its due date are specified.
+
+
+
+ This symbol
+
+
+
+ represents a task that begins
+
+
+
+ This symbol
+
+
+
+ represents a task that ends
+
+
+
+ Ths symbol
+
+
+
+ represents a task that begins and ends the
+ same day
+
+
+
+
+
+
+
+ Gantt chart
+
+ This diagramme shows tasks and their achievement rate.
+
+ Achievement is represented in blue. Delay in red.
+
+
+
+
+ Gantt chart
+
+
+
+
+
+
+
+
+
+
+
+ Issue management
+
+
+
+
+ Issue list
+
+ By default, the entire list of the project open Issues are
+ displayed. Various screens allow you to select the Issues to be
+ displayed. If the project has sub-projects, you have the possibility
+ to display the sub-project's Issues as well (not displayed by
+ default).
+
+ Once applied, a screen is valid during the entire session. You
+ can re-define it or delete it by clicking Cancel.
+
+
+
+
+ Request list
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Reports
+
+ This screen presents the number of Issues and Issue status
+ synthesis according to various criteria (tracker, priority, category).
+ Direct links allow for access to the detailed Issue list for each
+ criterion.
+
+
+
+ Change log
+
+ This page presents the entire list of the resolved Issues for each
+ version of the project. Certain types of Issues can be excluded from
+ this display.
+
+
+
+ News
+
+ Allows you to inform users on project activity.
+
+
+
+ Documents
+
+ Documents are grouped by categories (see Value Lists). A document
+ can contain several files (for example: revisions or successive
+ versions).
+
+
+
+ Files
+
+ This module allows you to display various folders (sources,
+ binaires, ...) for each version of the application.
+
+
+
+ Settings
+
+
+
+
+ Project features
+
+
+
+
+
+ Public : if it’s a
+ public project, it can be viewed (request consultation, documents
+ consultation, ...) for all the users, including those who are not
+ project members. If it’s not a public project, only the project
+ members have access to it, according to their role.
+
+
+
+ Customized fields :
+ Select the customized fields that you want to use. Only the
+ administrator can define new customized fields.
+
+
+
+
+
+
+
+ Members
+
+ This screen allows you to define the project members as well as
+ their corresponding roles. A user can have only one role in a given
+ project. The role of a member determines the permissions they have in
+ a project.
+
+
+
+ Versions
+
+ Versions allow you to follow the changes made during all the
+ project. For instance, at the close of an Issue, you can indicate
+ which version takes it into account. You can display the various
+ versions of the application (see Files).
+
+
+
+ Request categories
+
+ Issue categories allow you to organize Issues. Categories can
+ correspond to different project modules.
+
+
+
+
+
+ User accounts
+
+
+
+
+ My account
+
+
+
+
+ Information
+
+ This screen allows you to modify your account: lastname,
+ firstname, email address, language.
+
+ If Mail notifications is unchecked, no
+ email will be sent to you.
+
+
+
+ Password
+
+ To change your password, type your old password and your new
+ password (twice). Password length must be between 4 and 12
+ characters.
+
+ If your account uses an external authentication (LDAP), you
+ can't change your password in redMine.
+
+
+
+
+ My page
+
+ This page allows you to display various information about your
+ projects.
+
+ To personalize your page, click on Personalize this
+ page. Then you can choose which information to display and
+ where it is displayed.
+
+
+
+ Password lost
+
+ If you loose your forget, a procedure allows you to choose a new
+ one.
+
+ On the login screen, click on Lost password.
+ Type your email address and submit the form. An email is then sent to
+ you. It contains a link that allows you to change your password.
+
+ If your account uses an external authentication (LDAP), this
+ procedure isn't be available.
+
+
+
+ Register
+
+ By registering, you can get an account without the intervention of
+ the administrator.
+
+ On the login screen, click on Register. Fill
+ the form and submit it. An email will be sent to you. To activate your
+ account, use the link that is contained in this mail.
+
+ The possibility to register can be desactived in the application
+ configuration.
+
\ No newline at end of file
diff --git a/doc/docbook/fr/images/arrow_bw.png b/doc/docbook/fr/images/arrow_bw.png
new file mode 100644
index 00000000..c50fbce8
Binary files /dev/null and b/doc/docbook/fr/images/arrow_bw.png differ
diff --git a/doc/docbook/fr/images/arrow_from.png b/doc/docbook/fr/images/arrow_from.png
new file mode 100644
index 00000000..f1e1b6c3
Binary files /dev/null and b/doc/docbook/fr/images/arrow_from.png differ
diff --git a/doc/docbook/fr/images/arrow_to.png b/doc/docbook/fr/images/arrow_to.png
new file mode 100644
index 00000000..faef20c7
Binary files /dev/null and b/doc/docbook/fr/images/arrow_to.png differ
diff --git a/doc/docbook/fr/images/gantt.png b/doc/docbook/fr/images/gantt.png
new file mode 100644
index 00000000..65c33d68
Binary files /dev/null and b/doc/docbook/fr/images/gantt.png differ
diff --git a/doc/docbook/fr/images/issues_list.png b/doc/docbook/fr/images/issues_list.png
new file mode 100644
index 00000000..520de14b
Binary files /dev/null and b/doc/docbook/fr/images/issues_list.png differ
diff --git a/doc/docbook/fr/images/locked.png b/doc/docbook/fr/images/locked.png
new file mode 100644
index 00000000..5199dfe2
Binary files /dev/null and b/doc/docbook/fr/images/locked.png differ
diff --git a/doc/docbook/fr/images/roles_edit.png b/doc/docbook/fr/images/roles_edit.png
new file mode 100644
index 00000000..a1ed2755
Binary files /dev/null and b/doc/docbook/fr/images/roles_edit.png differ
diff --git a/doc/docbook/fr/images/user_new.png b/doc/docbook/fr/images/user_new.png
new file mode 100644
index 00000000..0c220257
Binary files /dev/null and b/doc/docbook/fr/images/user_new.png differ
diff --git a/doc/docbook/fr/images/users_list.png b/doc/docbook/fr/images/users_list.png
new file mode 100644
index 00000000..74d9c9a5
Binary files /dev/null and b/doc/docbook/fr/images/users_list.png differ
diff --git a/doc/docbook/fr/images/workflow.png b/doc/docbook/fr/images/workflow.png
new file mode 100644
index 00000000..04e79d61
Binary files /dev/null and b/doc/docbook/fr/images/workflow.png differ
diff --git a/doc/docbook/fr/redmine-userdoc-fr.xml b/doc/docbook/fr/redmine-userdoc-fr.xml
index ba52da2c..fa67a6a2 100644
--- a/doc/docbook/fr/redmine-userdoc-fr.xml
+++ b/doc/docbook/fr/redmine-userdoc-fr.xml
@@ -2,11 +2,17 @@
- Documentation redMine
+ DocumentationAdministration
+
+ Projets
+
+ Ces écrans vous permettent de gérer les projets.
+
+
Utilisateurs
@@ -28,18 +34,41 @@
- Les boutons Lock/Unlock vous permettent de
- vérouiller/dévérouiller les comptes utilisateurs.
+ Statut des comptes:
- Un utilisateur dont le compte est vérouillé ne peut plus
- s'identifier pour accéder à l'application.
+
+
+ L'icône
+
+
+
+ signifie que le compte est vérouillé. Un
+ utilisateur dont le compte est vérouillé ne peut plus s'identifier
+ pour accéder à l'application.
+
+
+
+ L'icône
+
+
+
+ signifie que le compte n'a pas encore été
+ activé par l'utilisateur .
+
+
+
+ Les boutons Vérouiller/Dévérouiller vous permettent de bloquer
+ ou débloquer les comptes utilisateurs.
+
+ Création ou modification d'un utilisateur
- En mode modification, laissez le champ Password vide pour
- laisser le mot de passe de l'utilisateur inchangé.
+ En mode modification, laissez le champ Mot de
+ passe vide pour laisser le mot de passe de l'utilisateur
+ inchangé.Un utilisateur déclaré comme administrateur dispose de toutes
les permissions sur l'application et sur tous les projets.
@@ -76,6 +105,20 @@
Sur l'écran d'édition du rôle, cochez les actions que vous
souhaitez autoriser pour le rôle.
+
+
+
+
+ Rôle et permissions
+
+
+
+
+
+
+
+
+
@@ -99,7 +142,12 @@
- Chaîne: chaîne de caractère
+ Texte: chaîne de caractères
+
+
+
+ Texte long: chaîne de caractères, avec
+ champ à plusieurs lignes
@@ -325,7 +373,7 @@
- Déclaration d'un annuaire LDAP
+ Annuaire LDAP
@@ -419,6 +467,71 @@
+
+ Planning
+
+
+
+
+ Calendrier du projet
+
+ Le calendrier présente les tâches qui commencent ou se terminent
+ au cours du mois sélectionné (mois en cours par défaut). Les tâches
+ correspondent aux demandes pour lesquelles la date de début et
+ d'échéance sont renseignées.
+
+
+
+ Le symoble
+
+
+
+ représente le début d'une tâche
+
+
+
+ Le symbole
+
+
+
+ représente la fin d'une tâche
+
+
+
+ Le symbole
+
+
+
+ représente une tâche qui débute et se
+ termine le jour même
+
+
+
+
+
+
+
+ Diagramme de Gantt
+
+ Le diagramme de Gantt représente pour la période choisie
+ l'ensemble des tâches et leurs taux d'avancement.
+
+ L'avancement est représenté en bleu. Le retard en rouge.
+
+
+ Diagramme de Gantt
+
+
+
+
+
+
+
+
+
+
+
+
Gestion des demandes
@@ -429,13 +542,11 @@
Par défaut, l'ensemble des demandes ouvertes du projet sont
affichées. Différents filtres vous permettent de sélectionner les
- demandes à afficher. Si le projet comporte des sous-projets, vous avez
- la possibilité d'afficher également les demandes relatives aux
- sous-projets (non affichées par défaut).
+ demandes à afficher.
Une fois appliqué, un filtre reste valable durant toute votre
session. Vous pouvez le redéfinir, ou le supprimer en cliquant sur
- Annuler.
+ Effacer.
@@ -513,9 +624,9 @@
Champs personnalisés: sélectionner les
- champs personnalisés que vous souhaitez utiliser pour les demandes
- du projet. Seul l'administrateur peut définir de nouveaux champs
- personnalisés.
+ champs personnalisésMo que vous souhaitez utiliser pour les
+ demandes du projet. Seul l'administrateur peut définir de nouveaux
+ champs personnalisés.
@@ -525,8 +636,8 @@
Membres
- Cet écran vous permet de définir les membres du projet ainsi que
- leurs rôles respectifs. Un utilisateur ne peut avoir qu'un rôle au
+ Cett section vous permet de définir les membres du projet ainsi
+ que leurs rôles respectifs. Un utilisateur ne peut avoir qu'un rôle au
sein d'un projet donné. Le rôle d'un membre détermine les permissions
dont il bénéficie sur le projet.
@@ -547,7 +658,92 @@
Les catégories de demande vous permettent de typer les demandes.
Les catégories peuvent par exemple correspondre aux différents modules
du projet.
+
+ Une catégorie référencée sur des demandes ne peut pas être
+ supprimée.
+
+
+
+
+ Comptes utilisateurs
+
+
+
+
+ Mon compte
+
+
+
+
+ Informations
+
+ Cet écran vous permet de modifier les informations relatives à
+ votre compte: nom, prénom, adresse mail, langue (Anglais, Allemand,
+ Espagnol ou Français).
+
+ Si la case Notifications par mail est
+ décochée, aucune notification par mail ne vous sera envoyée.
+
+
+
+ Changement de mot de passe
+
+ Pour changer votre mot de passe, saisissez votre mot de passe
+ actuel et le nouveau mot de passe souhaité (double saisie pour
+ confirmation). Le mot de passe doit avoir une longueur comprise entre
+ 4 et 12 caractères.
+
+ Si votre compte utilise une authentification externe (un
+ annuaire LDAP), vous ne pouvez pas changer votre mot de passe dans
+ redMine.
+
+
+
+
+ Ma page
+
+ Cette page vous permet d'afficher de manière synthétique des
+ informations sur vos projets.
+
+ Pour personnaliser votre page, cliquer sur le lien
+ Personnaliser cette page. Vous pouvez alors
+ sélectionner les informations à afficher et les positionner où vous le
+ souhaitez sur la page, par glisser-déposer.
+
+
+
+ Mot de passe perdu
+
+ En cas de perte de votre mot de passe, une procédure par mail vous
+ permet d'en choisir un nouveau.
+
+ Sur l'écran d'authentification, cliquez sur Mot de passe
+ perdu. Saisissez ensuite votre adresse mail dans le champ
+ prévu et validez. Un mail vous est alors transmis. Il contient un lien
+ qui vous permettra d'accéder à la page de choix du nouveau mot de
+ passe.
+
+ Si votre compte utilise une authentification externe (un annuaire
+ LDAP), cette procédure n'est pas disponible.
+
+
+
+ S'enregistrer
+
+ L'enregistrement vous permet d'obtenir un compte sans intervention
+ de l'administrateur.
+
+ Sur l'écran d'authentification, cliquez sur
+ S'enregistrer. Complétez le formulaire
+ d'inscription et validez. Un mail vous est alors transmis. Pour activer
+ votre compte, utilisez le lien présent dans le mail qui vous a été
+ envoyé.
+
+ La possibilité de s'enregistrer peut avoir été désactivée par
+ l'administrateur.
+
+
\ No newline at end of file
diff --git a/public/manual/en/ch01.html b/public/manual/en/ch01.html
index aa86147e..67447735 100644
--- a/public/manual/en/ch01.html
+++ b/public/manual/en/ch01.html
@@ -1,3 +1,3 @@
- Chapter 1. AdministrationredMine home
