These screens allow you to manage projects.
On this screen, you can archive or delete projects.
An archived project is no longer visible by users. It can be un-archived by the administrator.
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.
Subproject of: lets you define the parent project. The hierarchy of the projects is limited to 2 levels. A parent project cannot be itself a sub-project.
Name: project display name (must be unique).
Description: description that appears on the project overview.
Identifier: name of the project used in an internal way by the application (must be unique). Once the project created, this identifier cannot be modified.
Customized fields : Select the customized fields that you want to use. Only the administrator can define new customized fields.
A source repository can be associated with each project. Once the repository configured, you will be able to browse it and view the revisions. The revisions appear in the Activity view.
Each project can have its own wiki. To activate it, check the Wiki option in the project settings and give the name for the main page.
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 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).
Issue categories allow you to organize Issues. Categories can correspond to different project modules.