# List of Types

Each element of ProjeQtOr can be typed at your convenience according to your profession or your field of activity.

Each type is presented the same. A very simple description section, with different fields depending on the element,

and a behavior section that will condition your future actions according to the parameters entered.

## Behavior section

This section is common to several element types.

Allows to determine some GUI behavior, according to element types.

Description or Comments

- Box checked indicates the field Description is mandatory.

Responsible

- Box checked indicates the field Responsible is mandatory when the status to treatment of the item is “In progress”.

Result

- Box checked indicates the field Result is mandatory when the status to treatment of the item is “done”.

Flag status

- You can lock the macro status: In progress - Done - Closed - Canceled

- Those fields allow to determine whether the checkbox fields concerned are locked or not.

- If the box is checked then you will only be able to modify the macro status thanks to the workflow statuses.

No left work on done

- The plannable elements cannot be passed to status done if there is still left work.

### Project

Lead Project

- The definition is made by the project type, you define that certain types of projects can not have activities, only subprojects or milestones.

### Activity

activity on real time

- Possibility of managing activities on real time.

- See: Global parameters | Assignement section

No left work on done

- The activity cannot be passed to status done if there is still left work.

Todo list

- Checked box prohibits status change to completed if not all to-do list items are set to “completed”

### Ticket

Resolution

- Box checked indicates the field Resolution is mandatory when the status to treatment of an item is done.

Lock solved

- Box checked indicates the field Solved is read only.

- The value of field must come from the field “Solved” defined in the selected resolution.

Todo list

- Checked box prohibits status change to completed if not all to-do list items are set to “completed”

### Translation

Translation Request type

initial status of items

> The initial state of the lines corresponds to the state of the request which will result in the automatic generation of the translation lines according to the languages recorded on your product or component version.

translation delay (nb days)

> The translation deadline (in days) determines the deadline for the planned delivery date which will be calculated automatically from the creation of the request. This period is expressed in calendar duration and does not take into account non-working days.

Translation item type

status of generation of item

> Corresponds to the state in which the rows will be created.

## Types restrictions

> Allows to limit values displayed in the list of values for each element type.

> Restrictions can be defined for a project, a project type or a profile.

> Note

> Types restrictions section on Project screen

> To display types restrictions section: Go to Global parameter > Tab Activity > Controls and Restrictions Section “allow type restriction on project” must be set to “Yes”. Possibility to define more restrictions to a project against restrictions defined at the project type level.

> Type restriction management

> Restrict types section

> - Click on ``Restrict` `types`` button to display the dialog box.

> - For each element type, select values that will be in the list of values displayed.

> - By default, if no type of element is selected, all the values of the line will be displayed on each screen that will be affected.

> Displays element type names where a restriction is applied

> Reminder : It means too, no restriction for remainding element types on each dedicated screen.

## Description section

### Actions types

Action type is a way to define common behavior on group of actions.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Activities types

Activity type is a way to define common behavior on group of activities.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Default planning mode | Default planning mode for type.
Priority | Defined the priority of the activity type. It will be automatically applied in the activity management section.
Color | Defined the default color for this activity type.
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Asset types

Question type is a way to define common behavior on group of questions.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Budget types

Budget types are a way to define the best budget for each project/activity.

Estimated budget, cash, investment, sale …

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Call for tender types

The types of calls for tenders make it possible to define the best procedure for launching calls with respect to the organization of your company:

the open, restricted tender, with minimum capacity requirements or pre-selection;

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Catalog types

Catalog types allow you to defune what type of item you produce or sell to your customers: products, services …

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Change requests types

The change request type is a way to define common behavior on a group of particular requests.

Several types are pre recorded: recurring problems, technical and functional improvement, regulatory constraint and process and quality.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Client Bills types

Bill type is a way to define common behavior on group of bills.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Client contract types

Client contract types are a way of defining the type of contract with a client.

Types of contract are already pre-registered: management assistance, hosting, technical improvement or Maintenance and support

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Client order types

Client order types allow you to define common order behaviors, such as billing

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Client payments types

customer payment type defines how the customer will pay the bill

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Client quotations types

Customer quote types allow you to define common behaviors on a quote group, such as the type of billing that will be applied

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Components types

Component type is a way to define common behavior to group of component.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Component version types

Component version type is a way to define common behavior to group of Component version.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Contexts types

Context types are used to define the environmental context to describe ticket or test case.

Only three context types exist, corresponding to the three selectable fields: Environment, OS and Browser.

You can only rename the types, not add nor remove any.

Note

- Only the name of the context types can be changed.

- No new context type can be added.

- No context type can be deleted.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Description | Description of the type.
Closed | Box checked indicates the type is archived.

### Customers types

Customer type is a way to define different kinds of customers (prospects or clients).

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Decisions types

Decision type is a way to define common behavior on group of decisions.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Documents types

Document type is a way to define common behavior on group of documents.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Expenses details types

Expense detail type is a way to define common behavior and calculation mode on group of expense details.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Sort order | Number to define order of display in lists.
Value / unit | Define calculation mode for the detail type.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

Field Value / unit

- If unit is set and not value, this line will be imputable.

- If both unit and value are set, the line will be read only.

- Result cost will be the multiplication between each of the three non empty line values.

Field | Description
--- | ---
Individual expense | Details type of individual expense.
Project expense | Details type of project expense.

### Individual expenses types

Individual expense type is a way to define common behavior on group of individual expense.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Issues types

Issue type is a way to define common behavior on group of issues.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Meetings types

Meeting type is a way to define common behavior on group of meetings.

Note

Meeting type is also used for periodic meetings definition.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Messages types

Message type is a way to define common behavior on group of messages (appearing on today screen).

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Color | Display color for messages of this type.
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Milestones types

Milestone type is a way to define common behavior on group of milestones.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Default planning mode | Default planning mode for type.
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Opportunities types

Opportunity type is a way to define common behavior on group of opportunities.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Order to Provider types

Vendor order types categorize the subject of the request: service or product

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Organization types

The type of organization allows you to define a common behavior on organizations.

Management of Organizations allows to edit the structure of the company in the frame of organizations

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the project type.
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Payments to provider types

Payment type is a way to define common behavior on group of payments.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Planning poker session type

Planning poker session type is a way to define common behavior on group of planning poker.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Products types

Product type is a way to define common behavior to group of product.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Product version types

Product version type is a way to define common behavior to group of Product version.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Project expenses types

Project expense type is a way to define common behavior on group of project expense.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Projects types

Project type is a way to define common behavior on group of projects.

Code of the project type

  Some important behavior will depend on code of the project type.

OPE : Operational project

Most common project to follow activity.

All new types are created with OPE code.

ADM : Administrative project

Type of project to follow non productive work : holidays, sickness, training, …

Every resource will be able to enter real work on these projects, without having to be allocated to the project, nor assigned to project activities.

Assignments to all project task will be automatically created for users to enter real work.

These projects are not visible on Gantt type screens.

Some sections and fields are not visible or do not work on administrative projects like Paused, Fix planning or the minimum threshold.

TMP : Template project

These projects will not be used to follow some work.

They are just designed to define templates, to be copied as operational projects.

Any project leader (profile) can copy such projects, without having to be allocated to them.

PRP : Proposal project

These projects will not be used to follow some work.

This type of project makes it possible to define whether a project is strategically interesting to carry out.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the project type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Billing type | Will define billing behavior (see: Incomes).
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Provider bill types

There is a wide variety of invoice types. Each one is used in specific circumstances and requires the respect of protocols concerning their constitution and their emission.

You can create as many invoice types as you need.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Provider tender types

Quote types allow you to organize and categorize the different offers received by your suppliers

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Providers types

Provider type is a way to define different kinds of providers.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Questions types

Question type is a way to define common behavior on group of questions.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Requirements types

Requirement type is a way to define common behavior on group of requirements.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Risks types

Risk type is a way to define common behavior on group of risks.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Supplier contract types

Supplier contract types are a way of defining the type of contract with a supplier.

Types of contract are already pre-registered: management assistance, hosting, technical improvement or Maintenance and support

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Test cases types

Test case type is a way to define common behavior on group of test cases.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Test sessions types

Test session type is a way to define common behavior on group of test sessions.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Default planning mode | Default planning mode for type.
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Tickets types

Ticket type is a way to define common behavior on group of tickets.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Translation item types

Translation lines also have the possibility of being typed. You can more easily compartmentalize your requests.

Assign a different workflow and behavior for each type of line.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.

### Translation request types

You define the types of translation that you will use in your business.

This allows you to apply a different workflow and behavior for each type.

Required fields
Field | Description
--- | ---
Id | Unique Id for the type.
Name | Name of the type.
Code | Code of the type.
Workflow | Defined the workflow ruling status change for items of this type (see: Workflow).
Sort order | Number to define order of display in lists.
Closed | Box checked indicates the type is archived.
Description | Description of the type.