The Project settings screen (menu Projects › Project settings, or the button of the same name of the project list) defines the project types and priorities offered in the forms. It is reserved for administrators.
Supplied types and priorities
Three types are supplied (Standard project, IT project, Organizational project) and four priorities (Low, Medium, High, Critical). You can rename, edit or deactivate them: they are never rewritten or recreated. Priorities apply to projects and tasks.
Add or edit a type or a priority
In the Project types or Priorities card, click Add, or Edit next to a row, then fill in:
- Code: unique identifier, 50 characters at most. It is upper-cased and spaces become
_; - Order: position in lists;
- Active: only an active item is offered in the forms;
- Label: one field per active language of the instance. The default language's field, marked required, is mandatory.
For a project type, two more fields set the approval:
- Charter approval: None (the project manager activates the project), Simple (sponsor) (the sponsor approves, or else an administrator) or Process (a process decides);
- Approval process: mandatory with the Process mode (Choose the approval process.). The same process is used for phase gates that require approval. Without the Processes module, the list is empty and states No process available (Workflow module disabled or no process).
Click Save.
Good to know
- No deletion: a type or priority that should no longer be used is deactivated. Projects and tasks that carry it keep it.
- Deactivated value on a project: the project edit form only offers active types and priorities, plus the value the project already carries, even if deactivated. The message This value is deactivated: it is kept as long as you do not change it. points it out; saving the project keeps it.
- Project numbers: the box at the top of the screen shows the number prefix (
PRJby default, for examplePRJ-000012). It is changed in the System configuration screen (Administration › Instance and operations › Configuration): use + Add to add the setting with the keyProject:NumberPrefix. A prefix longer than 12 characters is ignored in favor ofPRJ. Only new projects use it. - Going live: types and priorities set on a test instance reach production through GOLIVE ("Project type", "Project priority"), with a type's approval process. A value deactivated in testing is deactivated in production too; a value deactivated in production is never reactivated there.
See also
- "Steer a project": create a project, charter and phase approval.