How do I create a project?

Project Settings


In this screen you can configure the basic settings for the selected project.

General settings

The following general settings are available:
  • Name: project display name (must be unique).
  • 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.
    Note: starting from unscheduled version version#6 projects can be unlimitedly nested.
  • Description: description that appears on the project overview.
  • 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.
  • Homepage: homepage-link that appears on the project overview.
  • 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.


You can define which of the configured trackers (thus also their respective workflows) you are able to use within this specific project.

  • Trackers: select the trackers that you want to use for issues of the project. Only the administrator can define new trackers.

Custom fields

  • 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.

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).


You can choose the modules you want to use for the project.

Disabling a module doesn’t delete the associated data. It only prevents users from accessing it. After a module is disabled, it can be re-enabled with all its data.
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.


This screen lets you define project members and their roles. Users can have multiple roles in a given project. Be sure to click the name and the role before adding.

Issue categories

Issue categories let you to organize issues. Categories can for example correspond to the different components of your project.

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.

The following properties are configurable for (each of the) issue categories:

  • Name: The text you want to be displayed to identify the issue category. This field is required.
  • Assigned to: The project member to who you want to auto-assign newly created issues in this category. This field is optional.


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 as well.

project-settings_information-tab.jpg (21.8 kB) , 12/01/2009 04:34 pm

Screen_shot_2010-01-14_at_5.05.01_PM.png (42.1 kB) , 01/14/2010 05:05 pm

Screen_shot_2010-01-14_at_5.07.21_PM.png (37.9 kB) , 01/14/2010 05:08 pm

Screen_shot_2010-01-14_at_5.13.27_PM.png (31.3 kB) , 01/14/2010 05:14 pm

Screen_shot_2010-01-14_at_5.16.48_PM.png (16.6 kB) , 01/14/2010 05:18 pm

Screen_shot_2010-01-14_at_5.21.30_PM.png (25.1 kB) , 01/14/2010 05:22 pm

aolissue.txt Magnifier (2.5 kB) grim swan, 12/29/2016 06:00 pm