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, the global parameter “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
- Click on “Restrict types” button to display the dialog box.
- For each element type, select values that will be in the list of values.

Displays element type names where a restriction is applied

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.
Note
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 some real work on such projects, without having to be affected to the project, nor assigned to project activities.
- Assignments to all project task will be automatically created for users to enter real work.
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 can copy such projects, without having to be affected to them.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Billing type | Will define billing behavior (see: Billing types). |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Tickets types¶
Ticket type is a way to define common behavior on group of tickets.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Activities types¶
Activity type is a way to define common behavior on group of activities.
Section: Description
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: Workflows). |
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. |
* Required field
Milestones types¶
Milestone type is a way to define common behavior on group of milestones.
Section: Description
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: Workflows). |
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. |
* Required field
Quotations types¶
Quotation type is a way to define the way the concerned activity should be billed.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Orders types¶
Order type is a way to define the way the activity references by the order will be billed.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Individual expenses types¶
Individual expense type is a way to define common behavior on group of individual expense.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Project expenses types¶
Project expense type is a way to define common behavior on group of project expense.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Expenses details types¶
Expense detail type is a way to define common behavior and calculation mode on group of expense details.
Section: Description
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. |
* Required field
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.
Section: Scope
Field | Description |
---|---|
Individual expense | Details type of individual expense. |
Project expense | Details type of project expense. |
Bills types¶
Bill type is a way to define common behavior on group of bills.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Payments types¶
Payment type is a way to define common behavior on group of payments.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Risks types¶
Risk type is a way to define common behavior on group of risks.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Opportunities types¶
Opportunity type is a way to define common behavior on group of opportunities.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Actions types¶
Action type is a way to define common behavior on group of actions.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Issues types¶
Issue type is a way to define common behavior on group of issues.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
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.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Decisions types¶
Decision type is a way to define common behavior on group of decisions.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Questions types¶
Question type is a way to define common behavior on group of questions.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Messages types¶
Message type is a way to define common behavior on group of messages (appearing on today screen).
Section: Description
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. |
* Required field
Documents types¶
Document type is a way to define common behavior on group of documents.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
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)
Note
- Only the name of the context types can be changed.
- No new context type can be added.
- No context type can be deleted.
Section: Description
Field | Description |
---|---|
Id | Unique Id for the type. |
Name | Name of the type. |
Description | Description of the type. |
* Required field
Requirements types¶
Requirement type is a way to define common behavior on group of requirements.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Test cases types¶
Test case type is a way to define common behavior on group of test cases.
Section: Description
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: Workflows). |
Sort order | Number to define order of display in lists. |
Closed | Box checked indicates the type is archived. |
Description | Description of the type. |
* Required field
Test sessions types¶
Test session type is a way to define common behavior on group of test sessions.
Section: Description
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: Workflows). |
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. |
* Required field
Customers types¶
Customer type is a way to define different kinds of customers (prospects or clients).
Section: Description
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. |
* Required field
Providers types¶
Provider type is a way to define different kinds of providers.
Section: Description
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. |
* Required field
Products types¶
Product type is a way to define common behavior to group of product.
Section: Description
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. |
* Required field
Components types¶
Component type is a way to define common behavior to group of component.
Section: Description
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. |
* Required field
Behavior section¶
This section is common to several element types.
Allows to determine some GUI behavior, according to element types.
Note
- Depending on the element type the following fields can be displayed.
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 “handled”.
Result
- Box checked indicates the field “Result” is mandatory when the status to treatment of the item is “done”.
Flag status
- Fields: Lock handled, Lock done, Lock closed and Lock cancelled
- Those fields allow to determine whether the checkbox fields concerned are locked or not.
- When a flag status is locked, move to this status through status change.
Ticket type¶
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.