Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Its purpose is to propose a unique tool to gather all the information about the projects.
The fact is that many Project Management softwares just focus on planning. But it is a
much too restrictive point of view. Of course planning is an important activity of Project
Management and is one of the keys to Project success, but it is not the only one.
Project Managers need to foresee all what can happen, measure risks, build action plan
and mitigation plan.
It is also important to track and keep traces of all what is happening to the Project :
incidents, bugs , change requests, support requests, ...
Work
Tickets follow-up, for short activity follow-up such as support or bug fixing.
Activities follow-up, for work needing to be planned such as development or evolution.
Milestones follow-up, to define key dates of the planning.
Action follow-up, with complete description, status and accountable assignment.
Hierarchic level management via links of Activities, Tickets or Milestones to parent
Activity.
Dependencies management between Activities, Milestones and Projects for accurate
planning.
Assignment of resources to activities.
Workload management.
Cost management.
Workflow definition for status change.
Links management, between almost any items (Activities, Tickets, Documents, )
Follow-up
Planning functionality, in a simple and understandable way, taking into account resource
capacity, resource affectation rate to project and resource assignment rate to activity.
Planning presentation for projects, activities, milestones and dependencies in a Gantt
view.
Resources and project portfolio Gantt planning views.
Workload follow-up for resources.
Printable reports, with graphics and possibility to export to PDF format.
Functional (2/5)
Financial
Individual expense.
Project expense.
Orders.
Bill management, with several billing modes, depending on project type.
Definition of activities price, for time & material billing.
Review logs
Meetings follow-up, with summary of status and minutes, including periodic meetings.
Decisions follow-up, with full description and origin reminder.
Questions management, to track exchanges and responses.
Links management, between Meetings and Decisions and Questions, or any other item.
Tools
Message management, to communicate to users through Today screen.
Import elements (tickets or else) from CSV or XLSX files.
Display of emails sent and alerts sent (see other).
Functional (3/5)
Environment
Projects definition.
Customers and contacts definition.
Resources definition, for people working on Project, gathered in Teams.
Users definition, for people connecting to the tool.
Recipient definition, for billing information.
Products and Product Versions definition.
Calendar definition to enter off days.
Security
Login management for restricted access.
Access Right Management, based on profiles completely customizable.
Full profiles definition and rights management for reading, creating, updating and
deleting.
Management of visibility of Cost and Work depending on profile.
Audited against most popular security threats
Functional (4/5)
Document management
Definition of directories to store documents.
Documents management, with version follow-up, upload and download functionalities.
Document approbation process.
Others
Today screen with summary data for project, list of work (to do list) and list of tasks to
follow-up. Today screen is completely configurable. Any report can be displayed on today
screen.
Advanced filter functionality, including sort capacity.
Administration functionalities.
Global parameters management screen.
User parameters management screen.
Traceability of each update on items, displayed on change history section of each item.
Different selectable color themes.
CSV Export of every lists.
PDF export of every printable report.
Export planning to MS-Project xml format.
Multi-Language.
Technical (1/3)
Easy to use
ProjeQtOr proposes a user friendly interface.
Rich Internet Application running as a light client, in a simple browser.
Multi-browser compatible (validated on IE 7 to 9, Firefox 3 to 7 and Chrome 5 to 14).
User friendly interface.
Using AJAX, page refresh is always limited to the target area, avoiding blank pages and
flickering.
General user interface is designed to conform to many usually used tools (such as
webmail) :
- menu on left hand,
- data on right hand, divided on top as list of items and at bottom as detail for selected
item.
Selecting an item in the list directly displays its detail.
Possibility to access to history of changes is offered on every item.
Notes management enables to attach comments to any item.
File attachment is proposed for most important items.
Multi-Language.
ProjeQtOr has been designed and developed by the first user of the tool, for his own use.
So, ergonomics for a day to day use is a major factor of design.
Technical (2/3)
Easy to install
ProjeQtOr uses very well known technologies : PHP / MySQL (or PostgreSql) / AJAX.
Set up only requires the usual trilogy : Apache, MySQL (or PostgreSql) , PHP.
Just use your favorite package : XAMPP, LAMP, WAMP, EasyPHP, ZEND Server ...
Required versions:
- Apache : any version, V2 or above is recommended,
- MySQL : any version, V5 or above is recommended,
or PostgreSql : any version above V8.4, V9.1 or above is recommended,
- PHP : 5.2 or above needed.
For information, ProjeQtOr has been developed successively with :
Easy PHP 2.0.0.0 [Apache V2.2.11, MySQL 5.1.30, PHP V5.2.8]
Easy PHP 5.3.8.1 [Apache V2.2.21, MySQL 5.5.16, PHP V5.3.8]
ZEND Server 4.0.5 Community Edition [Apache V2.2.12, MySQL 5.1.35, PHP V5.2.10]
XAMPP 1.7.7 [Apache V2.2.21, MySQL 5.5.16, PHP V5.3.8]
Automatic version management triggers Database structure updates at first run for any
new version.
Set-up screen at first run to define internal parameters (database access, default
parameters,...).
Most of the parameters updatable through a devoted screen.
Technical (3/3)
Easy to parameter
Every user parameter, every list of values may be changed through a devoted screen.
Default parameters are proposed, corresponding to most common needs.
Language selection, proposed on locale value, editable by user
(English, French and German for current version).
Easy to customize
As ProjeQtOr is proposed under open source GPL Licensing, you may adapt it to your
needs.
ProjeQtOr has been developed as a Framework, so it is very easy to add an element or
add a data or change display for an element.
Easy to monitor
Connections management : list of open sessions, possibility to close one session or all
sessions.
Open / Closure of application for maintenance operations.
Installation
Pre-requisites :
- http server
- PHP server (5.2 or over)
- MySQL database (5 or over) or PostgreSql database (8.4 or over)
For instance, you may try to set-up an EasyPHP server, including all required elements.
This set-up is not recommended for production purpose, but only for testing and evaluation
purpose.
You may also set-up a ZEND Server, including all required elements.
This set-up can be used for production purpose.
Set-up :
- Unzip projectorriaVx.y.z.zip to the web server directory
- Run application in your favorite browser, using http://yourserver/projectorria
- Enjoy !
Notice :
- At first run, configuration screen will be displayed.
- To run again configuration screen, just delete "/tool/parametersLocation.php" file.
- On first connection, database will be automatically updated, it may take several minutes.
Support :
- you may request support in the Forum of ProjeQtOr web site :
http://www.projeqtor.org
Configuration
Make sure to store your parameters.php file out of web access to avoid having your security
information stolen (for instance connection login to your database)
Parameters (1/5)
Fields filled in Configuration screen are first stored in parameters.php file. Here is the mapping.
Since V3.0, almost all the parameters have migrated to the database, and are updatable
through the Global Parameters screen.
Only Database configuration and debug log configuration are left in parameters.php file.
Parameters (2/5)
SMTP Port Port to talk to SMTP (mail) server (default is '25') $paramMailSmtpPort
[New in V1.2.0]
Sendmail program Path to program used to send mails. $paramMailSendmailPath
path To set only on issue to send mails, or if not using default sendmail program. [New in V1.2.0]
Since V3.0, almost all the parameters have migrated to the database, and are updatable
through the Global Parameters screen.
Only Database configuration and debug log configuration are left in parameters.php file.
Parameters (3/5)
Since V3.0, almost all the parameters have migrated to the database, and are updatable
through the Global Parameters screen.
Only Database configuration and debug log configuration are left in parameters.php file.
Parameters (4/5)
Max file size for Max file size for attached files. Size is in bytes (1024 * 1024 * MB). $paramAttachementMaxSize
attachment Default value is '2097152' = 1024 * 1024 * 2 = 2 MB.
Temp directory for Directory to store temporary images for reports . It may be any valid $paramReportTempDirectory
reports directory into the web structure (must be web-reachable). [New in V1.4.0]
Default is '../files/report/' and may be kept as is.
Memory limit For Set maximum memory size (in MB) for PDF generation. $paramMemoryLimitForPDF
PDF Default in 512. [New in V1.6.1]
Since V3.0, almost all the parameters have migrated to the database, and are updatable
through the Global Parameters screen.
Only Database configuration and debug log configuration are left in parameters.php file.
Parameters (5/5)
Parameter file name Name of the file where all previous parameters will be stored. Stored as
Default value is '../files/config/parameters.php' : as it is within web $parametersLocation in
structure, it must be changed for security reasons. parametersLocation.php file
Allow login from Definition whether connections can be validated through Ldap directory. $paramLdap_allow_login
Ldap Possible values are true or false. [New in V1.8.0]
If set to true, ProjeQtOr can log user from Ldap.
Ldap Search User DN of Ldap user used for search functionality. $paramLdap_search_user
For instance cn=Manager,dc=mydomain,dc=com [New in V1.8.0]
LDAP Search User Password of Ldap user used for search functionality. $paramLdap_search_pass
Password [New in V1.8.0]
Ldap filter Ldap filter to find used name . Must include %USERNAME% that will be $paramLdap_user_filter
replaced be the login user name. [New in V1.8.0]
For instance uid=%USERNAME%
Installing new version
Pay attention that if you are upgrading from version lower than 1.1.0, you must remove
last script closure (?>) in parameters.php file before upgrading.
You can upgrade twice (if needed) : update parameter table, reset the value of line
where parameterCode='dbVersion' to the previous version number and connect again.
If you then notice that some menu items have disappeared, just check for double entries
in habilitation table (last lines) and delete them (this should not happen since V1.5.0).
Connection
Login to the application uses a standard login screen : users must enter user name and
password.
Remember me function allows the
user to automatically reconnect
with current credentials without
prompting this screen.
Select disconnection on main
screen to get back to login form.
Just notice that on this screen users have the possibility to change their password, and it is
the only place where they can do this.
The administrator is able to reset the passwords to the default value (see parameters).
When a password has been reset to default value, the user must change it on first
connection.
For the first connection to a newly installed version of ProjeQtOr, just use the default account
: admin / admin
You must then go to user screen to create new users.
Dont forget to change the default password for admin user, or delete the admin
user.
Remember to always have a user with admin rights to be able to create new users
and change profiles.
Graphical User Interface (1/10)
Generality
Menu
area
Splitter
Splitter
Detail
area
Message
and
Info bar
hyperlink
area
Graphical User Interface (2/10)
Toolbars and else
Clicking on the Logo Area
will display the About
pop-up.
Replace logo : Just insert Click on the Help icon will
your own logo.gif at the open the online user manual,
root directory will to the page corresponding to
automatically replace the the actual screen, if existing
logo with your own in the manual.
The navigation buttons give access to previous and next items in the
history.
Through the project selector parameter icon, you can If you create new projects, or change
select to view closed projects. Closed projects will then rights so that Projects list appearing in
appear in the project selector list. This will also have the combo should change, changes will
effect that items of closed projects will be visible (they are appear only after disconnection /
hidden in other case). reconnection or after a refresh of the
list (see beside).
You can also change the project selector format: default
wbs like, or filtering select like.
The main area (right side of the screen) is generally divided in two parts : List area and Detail area.
The upper part lists all the object (for instance, here are tickets).
On top left part, the number of listed items is displayed (here = 66).
Rapid filtering fields are proposed : id, name and type (if significant for the object).
Any change on id and name will instantly filter data. Search is considered as contains, so typing 1 in id
will select 1, 10, 11, 21, 31 and so on.
Selecting a type in the combo box will restrict the list to the corresponding type (will request server).
Check the show closed items to list also closed items.
For more complex filtering, click on the filter button (see next page for details).
Click on the print button to get a printable version of the list, or . to export it to PDF format.
Click on the csv export to export all the data of the selected items into CSV format file.
Click on a line (any column) will display the corresponding item in the detail area.
Graphical User Interface (6/10)
Filters
Enter new clause in Active filter : in Add a filter or sort clause, select the name of the field, the operator and
the value for the clause. Then click on to add the clause to the filter criteria.
The operator can be sort to define a sort criteria, then possible values are ascending or descending.
Click on on a clause line to remove it.
Click on on the header of Filter criteria to remove all clauses. This can also be done by clicking the Clear
button.
When Filter criteria is correct, click on OK button to apply the filter to the list.
You can also click Cancel button to revert to previous filter.
At any step you can enter a filter name and click on to save the filter definition.
When filter is a list of values (with amongst operator), multi-value selection is possible using [CTRL] key.
Filters are defined and stored for a user and a type of item (a screen).
When a filter is applied to a type of item, coming back after moving to another type (another selection in the
menu) will apply the previously defined filter.
After disconnection, currently applied filter is lost, but stored filters are saved. Default filter (if selected) is also
stored and will be automatically applied on next connection.
Graphical User Interface (7/10)
Filters
You can reorder fields with drag & drop feature, using the selector area .
When a field is selected, you can change its width with the spinner button.
Width is in % of total list width. Minimum width is 1%. Maximum width is 50%.
The name width is automatically adjusted so that total list width is 100%.
Take care that name width cannot be less than 10%.
So, if you select to many columns or set columns width
too large, you may have total width over 100%.
This will be highlighted beside buttons.
This may lead to strange display, over page width, on
List, reports or pdf export, depending on browser.
It is possible to reset the list display to its default format using the button.
Graphical User Interface (8/10)
Detail
The Detail area present the detail of the selected in the list.
Click on to create new item, to save the changes, or to get a printable version of the detail,
to copy the current item, to cancel ongoing changes, to delete the item, to refresh the display
and to send detail of item by email.
On dependent items (for instance Notes), click on (in header) to add new, to edit and to delete.
When changes are ongoing, you can not select another item or another menu item.
Save or cancel ongoing changes first.
Every section is collapsible : click on the arrow icon to collapse/expand the section.
Graphical User Interface (9/10)
Combo Detail
On Combo List fields, users may have access Detail button .
Double click on the search
button will directly go to
the selected item (if any)
If element is selected in the combo, detail of element is displayed :
When this list comes from Add Link or Add Approver or Add version or Add Test Case Run, it is multi-
selectable (use [CTRL] or [SHIFT] to select several lines)
Some users wont see the detail button, but a goto button : click on this button will go to selected
item. A double click on detail button will have the same goto effect.
Display of Detail combo is managed by the administrator, through specific access mode.
Anyhow, user can only display, list and create items corresponding to his rights, defined in access mode
to data.
Graphical User Interface (10/10)
Alerts
You may receive some information displayed as pop-up on the bottom right corner of the screen.
Three kinds of information may be displayed :
INFORMATION WARNING ALERT
On alert pop-up, you can select to remind you in a given number of minute (message will close and appear
again in the given number of minutes), or just mark it as read to definitively hide it.
Themes (1/2)
ProjeQtOr
ProjeQtOr
ProjectOr RIA
(old style)
Themes (2/2)
Blue
Red
Green
Orange
Grey
Multilingual
ProjeQtOr is multilingual.
Each user can choose the language to display all the captions.
Of course, data is displayed as input, no translation is operated.
On the login screen, the locale of the browser is used to display captions.
When connected, the language selected (and saved) by the user is used.
When selecting new language, only refreshed data will use new selected language. For
instance, all menu items will be kept in the old language. To actualize, save parameters,
disconnect and reconnect.
Administrator can define the default language. This one is used on login screen.
It is also used as long as the connected user has not selected his favorite display language.
All the captions and messages are stored in an Excel file : /tool/i18n/nls/lang.xls.
To change (or correct) any data, on a windows set-up, open the file to its default place,
enabling macros.
Save-as, with the same name (to insure the default repository is the default one).
Click on generate button.
All the corresponding language files are automatically generated, in /tool.i18n/nsl
subfolders.
To translate to a new language, update one of the existing columns, test using the
corresponding locale, and when completed submit the file to support@projeqtor.org, to
have the new language integrated in the tool.
Current version manages English, French, German, Spanish, Portuguese, Russian and
Chinese.
Creation specificity
It may sometimes seem that you are not able to attach a file to your new ticket.
In fact, since a user can update a ticket, he is able to insert an attached file.
So this is not a question of habilitation.
The reason is that this functionality do not appear during creation.
You just have to save first to be able to attach a file.
This rule is valid for all depending items : Attachments, Notes, Assignments, Predecessor
elements, Successor elements and links between Risk, Actions and Issues.
Just one word : "save" first.
Since V1.3.0, you can rapidly save with [CTRL]+S, like in many office tools.
Since V1.3.0, you can rapidly save with [CTRL]+S, like in many office tools.
When updating an item, only updated fields are stored in the database. This means that
if two users are updating different fields of the same item, they dont crush values
updates by each other.
Delete specificity
After deleting an item, you will not be able to see it any more.
Data is physically deleted from the database.
Only the update history can then be access through dedicated reports.
Always consider setting an item to close status rather than deleting it. You will then not see
it on main screens, but will be able to fetch it, using the show closed item checkbox in lists,
and possibly re-activate it.
Deleting functionality should be reserve to remove invalid newly created items.
Most simple items (environment parameters, lists, ) can only be copied as is using the copy
button .
But for most complex items (Tickets, Activities, ) it is possible to copy them into new kind of
elements. For instance, it is possible to copy a Ticket (the request) into an Activity (the task to
manage the request). The way to do it is always through the copy button . But then new
form is proposed :
There, it is possible to select new kind of element, select new type (corresponding to the kind
of element), change the name, and select whether the initial element will be indicated as origin
of the copied one.
For main items, it is also possible to choose to copy links, attachments and notes.
For Projects and Activities, it is also possible to copy the hierarchic structure of activities (sub-
projects, sub-activities).
If copy succeeds, the new element is automatically accessed, whatever the kind of element.
This means that the list may change to represent the new kind of elements.
Mailing specificity
requestor the Contact defined as requestor on current item; sometimes appears as contact (on Quotation and Order
for instance) and sometimes have no meaning (for instance for Milestone).
Just notice that this receivers list definition also applies to Automatic Mails on event and
Indicators
Multiple update
To update several items in one operation, click on button (no update must be ongoing)
This will switch to new detail view :
At this step, although the list does not seem to have changed, but it is now multi-selectable :
Select lines of items you want to update, specify update and save : the update will be applied to
all the items (if possible) and a report will be displayed on the right of the Multiple mode detail
screen.
Checklist
If a checklist is defined for the current element, and possibly limited to the current type of the
element, a checklist button is displayed amongst the element action buttons.
Click on this button to open the checklist pop-up.
Each line can get an extra comment, as well a globally on the checklist.
Export
Every list can be exported into CSV format file using the export button .
This displays the Export pop-up when fields to export can be selected.
Messages :
Here are displayed the messages defined in the message section.
Projects :
A quick overview of the projects status. The projects list is limited to project visibility scope of the connected
user.
Progress display bar is based on work progress. Additional display is the overall progress manually selected.
Counted items can be the to do (not done), not closed (to do and done) or all (to do, done and closed). to
[CTRL]+S
do, done and closed status are based on corresponding checkboxes.
A progress bar on each item shows part of to do (red) compared to done and closed (green).
On mouse over the bar, detail of figures is displayed.
Global health of the project is also displayed as a Red, Amber, Green firelight.
Printing :
You can print Today screen using the button.
Parameters :
Except for Messages that are always displayed, you can select which today part is
displayed.
Click on button (the one on top right, dont mismatch with project selector similar
button) to check which part is displayed.
There you can define the period for tasks selection : it means that only items with due
date less than today plus this selected period will be displayed. No due date will display
all items. You can also choose to display or not items with no due date.
There you can also define tables to display on the today screen.
You can also sort items (just grab the selector on left most part of line). They will be
displayed on Today screen in the same order.
Extending :
You can select any report to be displayed on the Today screen.
To do this, just go to the selected report, select parameters, display result (to
check it is what you wish on today screen) and click on button to insert this
report with parameter on the today screen. Any unchanged parameter will be set
as default value.
These reports will be displayed on Today screen like other pre-defined parts.
In the Today parameters pop-up, these items can be selected and sorted like any
other part.
These items can also be deleted to completely remove then from the list.
Project (1/5)
You can also define sub-projects of a project. Then, project may not be real projects, but just organizational
breakdown corresponding to the organization.
or organizational : Project X
(for instance to manage
Project X
Project X Product V1 Maint.
access rights)
Project X Product V1 Evo.
Project X Project X Project X Product V1
Bug.
Product V1 Product V2 Project X Product V2 Dev.
Maintenance Development
Project X V1 can be
Project X Project X shared with a large scope
Product V1 Product V1 of users, while others will
be restricted to internal
Evolutions Bug Fixing team.
Project (2/5)
Fields
Field Description
Id Unique Id for the project. Automatically generated on creation.
Name Short name of the project. Mandatory.
Type Type of project. Will define billing type for project.
Customer The customer of the project (see related topic)
Bill contact Billing contact.
Project code Code of the project. Informative data.
Contract code Code of the contract of the project. Several projects may share
the same contract code. Informative data.
Is sub-project of Name of the top project if this project is a sub-project.
Sponsor Name of the sponsor of the project.
Manager Name of the resource who manages the project (Project
Leader).
Color Color of the project, to be displayed in some repots.
Status Status of the project.
Health status Global health status of the project, displayed on today screen.
Quality level Estimation of quality level of project (result of audits).
Trend Trend of global Project health.
Overall progress Overall progress to be selected in a defined list.
Field Description Fix planning Selector to fix the planning of the project, and its sub-projects.
Attachments (see related topic) When this checkbox is checked, running planning for all projects
will not change planning for this project.
Notes (see related topic)
Done Flag to indicate that project is been finished.
Change History (see related topic) Date of end is saved.
Closed Flag to indicate that project is archived. Project will not appear
Hyperlinks created as attachments on Projects : in lists any more, unless show closed is checked.
Cancelled Flag to indicate than project is cancelled.
Description Complete description of the project. The description can have
many lines. The field will auto-extend.
Field Description
The progress information will impact Planning calculation, and is also calculated during Planning calculation.
(see related topic)
Field Description
Requested start date Wished start date. One on the three values is automatically calculated, so that :
end date = start date + duration (in working days)
Requested end date Wished end date. By default, the duration is calculated (if the three values are entered)
Requested duration Wished duration (in working days).
Validated start date Committed start date : project should not start later. One on the three values is automatically calculated, so that :
end date = start date + duration (in working days)
Validated end date Committed end date : project should not end later. By default, the duration is calculated (if the three values are entered)
Validated duration Committed duration : project should not last longer.
Validated work / cost Committed work / cost : total work / cost of the project should not be more.
Assigned work / cost Sum of all the assigned work / cost for the assignments on the project. Read only.
Planned start date Calculated start date, taking into account all the constraints (see related topic). Read only.
Planned end date Calculated end date, taking into account all the constraints (see related topic). Read only.
Planned duration Calculated duration, taking into account all the constraints (see related topic). Read only.
planned duration = planned end date planned start date (in working days, whatever the workload unit)
Planned work / cost Calculated total work / cost needed to complete the task. Read only. planned = real + left
Real start date Date of the first real work input entered by an resource on the real work allocation screen. Read only.
Real end date If project is done, date of the last real work input entered by an resource on the real work allocation screen. Read only.
Real duration Calculated duration : real duration = real end date real start date (in working days). Read only.
Real work / cost Sum of all the work / cost really spent on the project , entered by resources on the real work allocation screen. Read only.
Left work / cost Left work / cost to complete the project . Sum of the left work / cost on the activities of the project. Read only. Read only.
Wbs Work Breakdown Structure. Hierarchical position of the project in the global planning.
Progress Actual progress of the work on project, in percent. Progress = real work / planned work * 100.
Expected Expected progress of work on project, in percent. Expected = real work / validated work * 100.
Project (5/5)
Dependencies
If Project A is predecessor of Project B, Project B is Status Actual status of the predecessor or successor.
Pay attention to the heavy constraints that adding a predecessor will bring to the project. You should for
instance restrict this use to link sub-projects of a main project.
In ProjeQtOr, documents will reference files item, that will be stored in the tool as versions.
So a document will always refer to a directory where the file is stored.
Field Description
Id Unique Id for the document. Reference is displayed after id.
Document Document reference calculated from format defined in the Global
reference Parameters screen
Project The project concerned by the document.
A document must be linked either to a project (for project
documentation) or to a product.
Product The product concerned by the document.
A document must be linked either to a project or to a product
(for product document).
Directory Place where the document is stored to organize document
structure.
The directory also defines the place where files will be physically
stored.
Type Type of document.
Name Short description of the document. Mandatory.
Author User or Resource or Contact who created the document.
Positioned by default as the connected user. Can be changed (for
instance if the author is not the current user).
Closed Flag to indicate that document is archived. Document will not
appear in lists any more, unless show closed is checked.
Field Description
Lock / Unlock Button to lock or unlock the document to preserve it from being
this editing, or new version added.
document When document is locked it cannot be modified. Only the user
who locked the document, or a user with privilege to unlock any
document, can unlock it.
Locked Flag to indicated that the document is locked. Read only.
Locked by User who locked the document (if locked). Read only.
Field Description Locked since Date and time when document was locked (if locked). Read only.
Field Description
Versioning Type of versioning for the document.
type This will impact the version number format for versions.
Last version Caption of the last version of the document
Status Status of the last version of the document
Field Description
File Locale file that will be uploaded as new version.
Mandatory on creation of version.
Last version Caption of the last existing version.
Update Importance of the update concerned by the new version.
A version can have a draft status, that may be removed
afterwards.
New version New caption for the created version.
Date Date of the version
Status Current status of the version.
Is a Flag to set that this version is the new reference of the
reference document. Should be checked when version is validated.
Only one version can be the reference for a document.
Reference version is displayed in bold format in the
versions list.
Description Description of the version.
May be used to describe updates brought by the version.
Document (4/4)
Approvers
Field Description
Id Id of the approver (not id of the resource)
Name Name of the approver
Status Status of the approval of the last version of document
It is also possible to send a reminder email to all the approvers who have not yet approved the document.
Ticket (1/3)
Indicator : As Ticket is indicatorable, you may see a small icon on top left of detail of an item.
Just move the mouse over the icon to display which indicator has been raised.
Ticket (2/3)
Fields
Field Description
Id Unique Id for the ticket. Reference is displayed after id.
Project The project concerned by the ticket. Mandatory.
Ticket type Type of ticket.
Name Short description of the ticket. Mandatory.
External External reference of the ticket. Free input.
reference Can be reference of the ticket in an extern bug tracker.
Urgency Urgency for treatment of the ticket, as requested by the issuer.
Creation Creation timestamp. Automatically generated on creation.
date/time Can be changed.
Issuer User who created the ticket.
Can be changed (for instance if creator is not the issuer).
Requestor Contact at the origin of the ticket.
Original version can be multi-valued. Duplicate Link to another ticket, to link duplicate tickets.
ticket
Just use the button to select multiple versions.
Context List of 3 items describing the context of the ticket.
The version with smaller id will appear in the select
Contexts are initialized for IT Projects as Environment, OS
list and is considered as the main version. and Browser.
Other versions are listed above. This can be easily changed in the Contexts definition screen
It is possible to remove an other version through Original Version of product where ticket has been identified.
the button . version
It is possible to set an other version as the main Description Complete description of the ticket. The description can have
version using the button . many lines. The field will auto-extend.
Simple Ticket is just a restricted view of Ticket, with limited write access to Description section, and limited
view on treatment section.
This view is dedicated to provide access to Ticket to users who should not be able to change treatment of
Tickets, such an External Team members, but can possibly create new ones.
Simple Ticket (2/3)
Fields
Field Description
Id Unique Id for the ticket. Reference is displayed after id.
Project The project concerned by the ticket. Mandatory.
Ticket type Although it is a mandatory field, no type of ticket is visible on
Simple Ticket.
Simple Ticket is always of default type : the first one in the list.
Name Short description of the ticket. Mandatory.
Urgency Urgency for treatment of the ticket, as requested by the issuer.
Creation Creation timestamp. Automatically generated on creation.
date/time Cannot be changed on simple ticket. Use ticket view.
Version can be multi-valued. Issuer User who created the ticket. Not visible although it is a
mandatory filed. Set as current user on creation.
Just use the button to select multiple versions.
Context List of 3 items describing the context of the ticket.
The version with smaller id will appear in the select
Contexts are initialized for IT Projects as Environment, OS
list and is considered as the main version. and Browser.
Other versions are listed above. This can be easily changed in the Contexts definition screen
It is possible to remove an other version through Version Version of product where ticket has been identified.
the button . Description Complete description of the ticket. The description can have
It is possible to set an other version as the main many lines. The field will auto-extend.
version using the button .
Simple Ticket (3/3)
Fields
Field Description
Status Actual status of the ticket. May be linked to a workflow.
Change of the status can have several impacts :
automatically sending emails,
automatically update Handled, Done or Closed,
some fields may become mandatory (see related topic) .
Responsible Resource who is responsible for the treatment of the ticket.
Due date Actual target date for solving the ticket. Automatically initialized
to Initial due date.
Except for status, all these fields are readonly and Handled Flag to indicate that ticket has been taken into account.
Timestamp of handling is saved.
can only be updated through the Ticket view. This generally means that Responsible has been named.
Done Flag to indicate that ticket has been treated.
Timestamp of completion is saved.
Closed Flag to indicate that ticket is archived. Ticket will not appear in
lists any more, unless show closed is checked.
Cancelled Flag to indicate than ticket is cancelled.
Target version The target version of the product that will deliver the object of
the ticket.
Result Complete description of the resolution of the ticket. The result
can have many lines. The field will auto-extend.
Field Description
Linked elements (see related topic)
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Activity (1/5)
An activity is a kind of task that must be planned, or that regroups other activities.
It is generally a long time activity, that will be assigned to one or more resources.
Activities will appear on Gantt planning view.
For instance, you can manage as activities :
planned tasks,
change requests,
phases,
versions or releases,
Resources are can be assigned to activities. This means that some work is planned on this activity for the
resources. Only resources affected to the project of the activity can be assigned to the activity.
Activities can have predecessors and successors, to generate dependencies. Predecessors and successors can
be Activities, Milestones or Projects.
If activity A is predecessor of activity B, activity B is automatically successor of activity A.
Predecessors and successors must belong to the same project or be a project.
It is generally advised to split activities so that each unitary one is 1 to 10 days long.
Shorter tasks will lead to unnecessary heavy and complex planning.
Longer tasks will be difficult to follow and estimate in progress : the resources will have difficulties to
estimate left work.
Indicator : As Activity is indicatorable, you may see a small icon on top left of detail of an item.
Just move the mouse over the icon to display which indicator has been raised.
Activity (2/5)
Fields
Field Description
Id Unique Id for the activity. Reference is displayed after id. Status Actual status of the activity. May be linked to a workflow.
Change of the status can have several impacts :
Project The project concerned by the activity. Mandatory.
automatically sending emails,
Activity type Type of activity. automatically update Handled, Done or Closed,
Name Short description of the activity. Mandatory. some fields may become mandatory (see related topic) .
External External reference of the activity. Free input. Responsible Resource who is responsible for the treatment of the activity.
reference Can be reference of the activity in an extern tool Responsible must be a resource affected to the project.
Creation date Creation date. Automatically generated on creation. Handled Flag to indicate that activity has been taken into account.
Can be changed. Date of handling is saved.
This generally means that Responsible has been named.
Issuer User who created the activity.
Done Flag to indicate that activity has been treated.
Can be changed (for instance if creator is not the issuer).
Date of completion is saved.
Requestor Contact at the origin of the activity.
Closed Flag to indicate that activity is archived. Activity will not appear
Origin Origin element (may be automatically inserted on copy). in lists any more, unless show closed is checked.
Description Complete description of the activity. The description can have Cancelled Flag to indicate than activity is cancelled.
many lines. The field will auto-extend.
Target version The target version of the product that will deliver the object of
the activity.
Field Description Result Complete description of the treatment done on the activity.
The result can have many lines. The field will auto-extend.
Linked elements (see related topic)
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Activity (3/5)
Assignments
The progress information will impact Planning calculation, and is also calculated during Planning calculation.
Field Description
Requested start date Wished start date. One on the three values is automatically calculated, so that :
end date = start date + duration (in working days)
Requested end date Wished end date. By default, the duration is calculated (it the three values are entered)
Requested duration Wished duration (in working days).
Validated start date Committed start date : activity should not start later. One on the three values is automatically calculated, so that :
end date = start date + duration (in working days)
Validated end date Committed end date : activity should not end later. By default, the duration is calculated (it the three values are entered)
Validated duration Committed duration : activity should not last longer.
Validated work / cost Committed work / cost : total work / cost of the activity should not be more.
Assigned work / cost Sum of all the assigned work / cost for the assignments on the activity. Read only.
Planned start date Calculated start date, taking into account all the constraints (see related topic). Read only.
Planned end date Calculated end date, taking into account all the constraints (see related topic). Read only.
Planned duration Calculated duration, taking into account all the constraints (see related topic). Read only.
planned duration = planned end date planned start date (in working days, whatever the workload unit)
Planned work / cost Calculated total work / cost needed to complete the task. Read only. planned = real + left
Real start date Date of the first real work input entered by an resource on the real work allocation screen. Read only.
Real end date If activity is done, date of the last real work input entered by an resource on the real work allocation screen. Read only.
Real duration Calculated duration : real duration = real end date real start date (in working days). Read only.
Real work / cost Sum of all the work / cost really spent on the activity, entered by resources on the real work allocation screen. Read only.
Left work / cost Left work / cost to complete the activity. Sum of the left work / cost on the assignments on the activity. Read only. Read only.
Priority Priority of the activity. Smaller priority activities are planned first (see related topic).
Planning Planning mode for the activity, forcing the way the activity will be planned (see related topic).
Wbs Work Breakdown Structure. Hierarchical position of the activity in the global planning.
Progress Actual progress of the work on activity, in percent. Progress = real work / planned work * 100.
Expected Expected progress of work on activity, in percent. Expected = real work / validated work * 100.
Activity (5/5)
Dependencies
In ProjeQtOr, two main types of Milestones exist depending on selected Planning Mode :
floating milestone : the milestone will automatically move to take into account dependencies,
fixed milestone : the milestone is fixed in the planning, not taking into account predecessor
dependencies. This kind of milestone is interesting for instance to set-up start date for some tasks.
Indicator : As Milestone is indicatorable, you may see a small icon on top left of detail of an item.
Just move the mouse over the icon to display which indicator has been raised.
Milestone (2/4)
Fields
Project The project concerned by the milestone. Mandatory. Status Actual status of the milestone. May be linked to a workflow.
Milestone Type of milestone. Change of the status can have several impacts :
type automatically sending emails,
Name Short description of the milestone. Mandatory. automatically update Handled, Done or Closed,
some fields may become mandatory (see related topic) .
Creation date Creation date. Automatically generated on creation.
Can be changed. Responsible Resource who is responsible for the treatment of the milestone.
Issuer User who created the milestone. Handled Flag to indicate that milestone has been taken into account.
Date of handling is saved.
Can be changed (for instance if creator is not the issuer).
This generally means that Responsible has been named.
Origin Origin element (may be automatically inserted on copy). Done Flag to indicate that milestone has been treated.
Description Complete description of the milestone. The description can have Date of completion is saved.
many lines. The field will auto-extend.
Closed Flag to indicate that milestone is archived. Milestone will not
appear in lists any more, unless show closed is checked.
Field Description
Requested due date Wished end date.
Validated due date Committed end date : milestone should not end later.
Planned due date Calculated end date, taking into account all the constraints (see related topic). Read only.
Real due date Real end date, when milestone is set to done.
Planning Planning mode for the milestone , forcing the way the milestone will be planned (see related
topic).
Wbs Work Breakdown Structure. Hierarchical position of the activity in the global planning.
Milestone (4/4)
Dependencies
The actions are the main activities of the risk management plan.
They must be regularly followed-up.
Indicator : As Action is indicatorable, you may see a small icon on top left of detail of an item.
Just move the mouse over the icon to display which indicator has been raised.
Action (2/2)
Fields
Field Description
Id Unique Id for the action. Reference is displayed after id. Field Description
Project The project concerned by the action. Mandatory. Status Actual status of the action. May be linked to a workflow.
Change of the status can have several impacts :
action type Type of action.
automatically sending emails,
Name Short description of the action. Mandatory.
automatically update Handled, Done or Closed,
Creation date Creation date. Automatically generated on creation. some fields may become mandatory (see related topic) .
Can be changed.
Responsible Resource who is responsible for the treatment of the action.
Issuer User who created the action.
Initial due date Initially expected end date of the action.
Can be changed (for instance if creator is not the issuer).
Attachments (see related topic) Result Complete description of the treatment of the action.
The result can have many lines. The field will auto-extend.
Notes (see related topic)
Change History (see related topic)
Real work allocation
This screen is devoted to input of real work. The input is for one resource, on a weekly basis.
Depending on rights management, users call only select themselves as a resource, or select any resource
affected to a managed project. Just changing year and/or week will display the corresponding sheet.
The period can also be selected through the a calendar, by selecting the 1st day of week.
Resource enters work day by day, on each affected activity. If daily work is more than the resource capacity,
it is displayed in red background to point this out.
A global comment can be added on the weekly follow-up.
This control is not blocking.
If it is equal to capacity, its background is green.
Left work is automatically decreased on input of real work, but it is important that resources think of updating
this data to reflect the really estimated left work. This way, planning can be efficient.
The cost corresponding to the work is automatically updated to the assignment, activity and project.
The icon indicates there is a comment on the assignment. Just move the mouse over the activity to see the
comment.
One line is displayed for each affectation, displaying the name of the activity.
As it is possible to affect several times the same resource on one activity, it is possible to have several lines for
the same activity, with the same name. The function, displayed in blue after the name, may then differ.
Planned work is indicated over each input cell, on top right corner, in light blue color.
This data can be hidden by un-checking the corresponding checkbox.
When resource has finished weekly input, he can validate it to submit it to the Project Leader .
The Project Leader will then have possibility to validate the work follow-up .
This will lock input for the corresponding week and resource.
Planning (1/5)
You can change the scale to have a daily, weekly or monthly view of the chart.
You can select to show tasks WBS before the names.
You can select to show resource name or initials (depending on parameter) on right on tasks.
You can change the starting or ending date to display the chart.
You can also choose to save these dates to retrieve the same display on every connection.
You can select the columns displayed on the left part of the chart, except for the name
of tasks (always displayed).
You can reorder columns with drag & drop on the handle in the selection list.
You can directly create a Project or an Activity or a Milestone using the create button.
As WBS is taken into account for planning priority, you may wish
to change tasks order.
This can simply be done with a drag & drop method on tasks,
using the handle on leftmost part of the task line.
You can change level of tasks this way (new since V4.3).
You can also increase or decrease indent of task using corresponding buttons
If a resource is assigned to several projects, re-calculation for one will not impact the planning for the
others, so new calculation will only use available time slots.
Use correct resource affectation rate to manage multi-projects affectations.
If the planning of one project must not be impacted by new calculation, you can use the fix planning
flag on this project. This will avoid to change planned values for this project and its subprojects.
Planning (3/5)
All the left work is planned, from starting date, to the max date to be able to plan the work.
Calculation is executed task by task, ordering thanks to :
- dependencies (if an activity has a predecessor, the predecessor is calculated first),
- planning mode : regular between dates are planned first
- priority : the smaller values are calculated first
if projects have different priorities, all tasks of project with smaller value priority are planned first.
- WBS : smaller WBS are planned first, so that planning is done from top to bottom of Gantt
Planning will distribute left work on future days, taking into account several constraints :
A resource is affected to a project, at a certain rate, possibly with start and end dates
If resources are not shared between projects, so rate will probably always be 100%.
But if resources are shared, then rate could be less than 100%. If a resource is equally shared between two
projects, then each project should enter a rate of 50%. This will lead to control that planning for each
project will not overtake rate capacity, so that first project planning its activity will not take all the
availability of the resource.
Project affectation capacity is controlled on a weekly basis. This means that planning for a project (including
sub-projects) will not be more than (Resource Capacity) x (Resource affectation rate) x 5 for a given
week.
Planning (4/5)
So, in Progress section (of Activity or Project) columns planned, real and left
are read only.
Since V4.5.0, affectations may have start and end dates. So, for a given assignment planned work will not
start before affectation start date on project of the activity and will stop on affectation end date.
This can lead to incompletely planned tasks. These would appear as brown bars in the Gantt view.
Projects portfolio
This is a good way to display projects synthesis and projects dependencies, without messing with projects
activities..
It is possible to select milestones to be displayed, from none to all, or select one milestones type to display
only milestones of this type .
Resource Planning
One group line can be display for projects level, depending on selection .
One line is displayed per activity. The Gantt bars for activities are hare split in two : real work in grey, planned
work in green. This makes appear some planning gap between started work and planned work.
Links between activities are displayed only into the resource group. Links existing between tasks on different
resources are not displayed.
Left work can be displayed on the right of task bars, using corresponding selection .
Planning can be displayed on a calendar view. This view can be monthly, weekly or daily.
One group line can be display for projects level, depending on selection .
Just click on any item to directly access the description of the item.
A requirement must be defined for a Product and/or a project (at least one of both must be selected).
A requirement can also be defined for a given version of the product, meaning the rule is valid since this
target version.
Linking requirements to a project will limit the visibility, respecting rights management at project level.
Requirements can be linked to many items (like other items), but the most interesting are links to test cases.
Linking a requirement to a test case will display summary of test case run (defined in test session). This way,
you will have instant display of test coverage for the requirement.
A requirement can be locked to ensure that its definition is not changed during the implementation process.
Only the user who locked the requirement or a habilitated user can unlock a requirement.
Field Description
Lock / Unlock Button to lock or unlock the requirement to preserve it from
requirement being changed.
When requirement is locked it cannot be modified. Only the
user who locked the requirement , or a user with privilege to
unlock any requirement , can unlock it.
Locked Flag to indicated that the requirement is locked. Read only.
Locked by User who locked the requirement (if locked). Read only.
Locked since Date and time when requirement was locked (if locked).
Read only.
Requirement (2/3)
Fields
Field Description
Id Unique Id for the requirement. Reference is displayed after id.
Project The project concerned by the requirement. Mandatory if Field Description
product is not set.
Top requirement Parent requirement, defining a hierarchic structure.
Product The product concerned by the requirement. Mandatory if
Status Actual status of the requirement. May be linked to a workflow.
project is not set.
Responsible Resource who is responsible of the requirement.
Requirement Type of requirement.
type Criticality Level of criticality of the requirement for the product.
Name Short description of the requirement. Feasibility Result of first analysis to check the feasibility of the
External External reference for the requirement (for instance the implementation of the requirement.
reference reference in a external requirement tool) Technical risk Result of first analysis to measure the technical risk of the
Creation Creation date and time. Automatically generated on creation. implementation of the requirement.
date/time Can be changed. Estimated effort Result of first analysis to measure the estimated effort of the
implementation of the requirement.
Requestor Contact who requested the requirement
Handled Flag to indicate that requirement has been taken into account
Urgency Urgency of implementation of the requirement. (first analysis is done). Date of handling is saved.
Description Complete description of the requirement. The description can Done Flag to indicate that requirement has been treated.
have many lines. The field will auto-extend.
Date of completion is saved.
Field Description Closed Flag to indicate that requirement is archived. Requirement will
not appear in lists any more, unless show closed is checked.
Linked elements (see related topic)
Cancelled Flag to indicate than requirement is cancelled.
Attachments (see related topic)
Target version Version of the product where the requirement will be active.
Notes (see related topic)
Result Description of the implementation of the requirement.
Change History (see related topic) The result can have many lines. The field will auto-extend.
Requirement (3/3)
Dependencies
Requirements can be linked to many kinds of item, including test cases (cases to tests the requirement).
A Ticket is automatically linked when a test linked to the requirement is set to status failed.
When test cases are linked to a requirement, the progress section summarizes the status of theses tests.
Summary : global status of tests linked to the requirement, as appering in all tests sessions including
the tests.
failed = at least one test failed
blocked = no test failed, at least one test blocked
planned = no test failed or blocked, at least one test planned
passed = all tests passed
not planned = no test linked
Linked = number of test cases linked to the requirement
Total : number of test cases on a test session whatever the status of the test case
(because a test case can be linked to several test sessions, Total can be greater than Linked)
Planned, Passed, Blocked, Failed : number of test cases on a test session in the corresponding status.
Issues : number of tickets linked to the requirement
A test case must be defined for a Product and/or a project (at least one of both must be selected).
A test case can also be defined for a given version of the product, meaning the test is valid since this version.
Linking test case to a project will limit the visibility, respecting rights management at project level.
In the test case screen, youll find a complete list of test case run. These are links of the test to test sessions.
You cannot change links or status here, you must go to the corresponding test session.
Test case (2/3)
Fields
In the test case screen, youll find a complete list of test case run. These are links of the test to test
sessions. This list also displays the current status of the test in the sessions.
You cannot change links or status here, you must go to the corresponding test session.
Field Description
Linked elements (see related topic)
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Test session (1/3)
A test session defines all the tests to be executed to reach a given target.
When running the test, you be able to easily change the status of the test run.
Test cases are added to the test session. Once added, you can quickly get description, prerequisite and
expected result of the test just moving the mouse over the corresponding , and icons.
You can quickly change the status of the test case with the corresponding icons :
to set status as passed
to set status as blocked
to set status as failed;
the edit screen is opened
to select the ticket describing
the incorrect behavior
Test session (2/3)
Fields
Field Description
Field Description
Id Unique Id for the test session. Reference is displayed after id. Parent activity Parent activity, to define hierarchic position in the Gantt
Project The project concerned by the test session. Mandatory if product Parent session Parent session, to define session of sessions
is not set.
Status Actual status of the test session. May be linked to a workflow.
Product The product concerned by the test session. Mandatory if project
Responsible Resource who is responsible of the test session.
is not set.
Handled Flag to indicate that session has been taken into account (first
Product Version of the product where the test session will be valid.
analysis is done). Date of handling is saved.
version
Done Flag to indicate that session has been treated.
Session type Type of test session.
Date of completion is saved.
Name Short description of the test session .
Closed Flag to indicate that session is archived. Session will not appear
External External reference for the test session (for instance the in lists any more, unless show closed is checked.
reference reference in a external test tool)
Cancelled Flag to indicate than test session is cancelled.
Creation Creation date and time. Automatically generated on creation.
date/time Can be changed. Result Summary result of the test session.
The result can have many lines. The field will auto-extend.
Description Complete description of the test session. The description can
have many lines. The field will auto-extend.
Field Description
Field Description
Linked elements (see related topic)
Assignment Resources can be assigned to Test sessions, exactly in the same
Attachments (see related topic)
way as assignment to activities.
Notes (see related topic) See activities for more information on assignment.
Change History (see related topic)
Test session (3/3)
Dependencies
When test cases are added to a test session, the Test cases part of the progress section summarizes the
status of theses tests.
Summary : global status of runs of tests added to the session:
failed = at least one test failed
blocked = no test failed, at least one test blocked
planned = no test failed or blocked, at least one test planned
passed = all tests passed
not planned = no test added
Total : number of test cases on the test session whatever the status of the test case
Planned, Passed, Blocked, Failed : number of test cases on the test session in the corresponding
status.
Issues : number of tickets linked to the test session
An quotation is a proposal estimate sent to customer to get approval of whats to be done, and how must the
customer will pay for it.
On the quotation form, you can record all the information of the sent proposal, including attaching some file
completely describing the proposal with details terms and conditions.
A quotation can be copied into an order when corresponding document is received as customer agreement.
Quotation (2/2)
Field Description
Id Unique Id for the quotation. Reference is displayed after id.
Project The project concerned by the quotation. Field Description
Type Type of quotation. Status Actual status of the quotation. May be linked to a workflow.
Name Short description of the quotation. Mandatory. Responsible Resource who is responsible for the quotation.
Issuer User who recorded the quotation Send date Date when quotation is sent to customer contact
Origin Element which is the origin of the quotation Offer validity Limit date of the validity of the proposal
Customer Customer concerned by the quotation Handled Flag to indicate that quotation is taken into account.
Contact Contact in customer organization to who you sent the quotation Done Flag to indicate that quotation is done (execution processed).
Description Complete description of the quotation. The description can have Closed Flag to indicate that quotation is archived. quotation will not
many lines. The field will auto-extend. appear in lists any more, unless show closed is checked.
Additional Any additional information about the quotation. Planned work Work days corresponding to the quotation.
info
PPD Price Per Day for the quotation. It represent the cost of one
work day.
Planned amount Total amount of the quotation. Amount = Work * PPD
Planned end Target end date of the activity object of the quotation.
date
Field Description Activity type Type of the activity object of the quotation.
NB : the activity should be created only after approval.
Attachments (see related topic)
Comments Comment about the treatment of the quotation.
Notes (see related topic)
On the order form, you can record all the information of the received order.
An order can be linked to an activity. It then represents the command of the work on the activity.
In that case, validated work of the activity is the sum of the orders linked to the activity.
Order (2/2)
Field Description
Linked activity Activity representing the execution of the order.
Field Description Status Actual status of the order. May be linked to a workflow.
Id Unique Id for the order. Reference is displayed after id. Responsible Resource who is responsible for the order.
Project The project concerned by the order. Handled Flag to indicate that order is taken into account.
Type Type of order. Done Flag to indicate that order is done (execution processed).
Name Short description of the order. Mandatory. Closed Flag to indicate that order is archived. Order will not appear in
lists any more, unless show closed is checked.
Customer Customer concerned by the quotation
Work Work days corresponding to the order.
Contact Contact in customer organization to who you sent the quotation
PPD Price Per Day for the order. It represent the cost of one work
External External reference of the order (as received). Mandatory. day.
reference
Amount Total amount of the order. Amount = Work * PPD
Submitted Date when order was sent, corresponding to customer approval
Activity type Type of the activity object of the quotation.
date date
NB : the activity should be created only after approval.
Issuer User who recorded the order
Comment Comment about the treatment of the order.
Origin Element which is the origin of the order
Description Complete description of the order. The description can have Field Description
many lines. The field will auto-extend.
Attachments (see related topic)
Start date Initial start date of the execution of the order.
Notes (see related topic)
End date Initial and validated end date of the execution of the order
Change History (see related topic)
Additional Any additional information about the order.
info
Individual Expense (1/3)
An individual expense stores information about individual costs, such as travel costs or else.
Field Description
Attachments (see related topic)
A project expense stores information about project costs that are not resource costs.
Field Description
Attachments (see related topic)
A term has triggers : the activities that should be billed at this term.
You may or may not insert activities as triggers.
This is a help (as a reminder) as the summary for activities is displayed for validated and planned amount and
end date. You can then define the term amount and date corresponding to these data.
Field Description
Type Type of the trigger (activity, milestone or project)
#id Id of the trigger
Name Name of the trigger
Status Current status of the trigger
Field Description
Notes (see related topic)
The defined billing types taken into account in the tools are :
At terms : a term must be defined to generate the bill, generally following a billing calendar.
Used for instance for : Fixed price projects.
On produced work : no term is needed, the billing will be calculated based on produced work for
resources on selected activities, on a selected period.
Used for instance for : Time & Materials projects.
On capped produced work : no term is needed, the billing will be calculated based on produced
work for resources on selected activities, on a selected period, taking into account validated work
so that total billing cannot be more than validated work.
Used for instance for : Capped Time & Materials projects.
Manual billing : billing is defined manually, with no link to the project activity.
Used for instance for : any kind of project where no link to activity is needed.
Field Description
Notes (see related topic)
At terms
Field Description
N Number of the line for the bill
Quantity Quantity of billed element
Description Description of the line. Automatically created
depending on billing type. Can be modified on update.
Detail Detail of the line. Automatically created depending on
billing type. Can be modified on update.
On produced work & On capped produced work Price Unitary price of billed element.
Sum Total price for the line = Price x Quantity
Term Billed term for At terms bill.
Resource Resource whose work is billed for on produced work
bill
Activity price Activity price defining the billed activity type for on
produced work bill
Start date Start date of the period to take into account work to
be billed for on produced work bill
End date End date of the period to take into account work to
be billed for on produced work bill
Activity price defines daily price for activities of a given Activity type and a given project.
This is used to calculate bill amount for billing type On produced work.
Field Description
Id Unique Id for the Activity price.
Project The project concerned by the Activity Price. Mandatory.
Activity type Type of activities concerned by the Activity Price. Mandatory.
Name Short description of the Activity price. Mandatory.
Price of the Daily price of the activities of the given activity type and the
activity given project
Sort order Number to define order of display in lists
Closed Flag to indicate that Activity Price is archived. Activity Price will
not appear in lists any more, unless show closed is checked.
Risk (1/2)
A risk is any threat of an event that may have a negative impact to the project, and which may be neutralized,
or at least minimized, through pre-defined actions.
Field Description
Status Actual status of the risk. May be linked to a workflow.
Change of the status can have several impacts :
automatically sending emails,
Field Description
automatically update Handled, Done or Closed,
Id Unique Id for the risk. Reference is displayed after id. some fields may become mandatory (see related topic) .
Project The project concerned by the risk. Mandatory. Responsible Resource who is responsible for the treatment of the risk.
Type Type of risk. Priority Expected priority to take into account this risk.
Name Short description of the risk. Mandatory. Initial end date Initially expected end date of the risk.
Creation date Creation date. Automatically generated on creation. Planned end Updated end date of the risk.
Issuer User who created the risk. date
Can be changed (for instance if creator is not the issuer). Handled Flag to indicate that risk has been taken into account.
Origin Origin of the risk. Can be any other item of the project. Date of handling is saved.
This generally means that Responsible has been named.
Cause Description of the event that may trigger the risk.
Done Flag to indicate that risk has been treated.
Impact Description of the estimated impact on the project if the risk Date of completion is saved.
occurs.
Closed Flag to indicate that risk is archived. Risk will not appear in
Severity Level of importance of the impact for the project. lists any more, unless show closed is checked.
Likelihood Probability level of the risk to occur. Result Complete description of the treatment done on the risk.
The result can have many lines. The field will auto-extend.
Criticality Global evaluation level of the risk.
Field Description
Automatically calculated from Severity and Likelihood values.
Can be changed Linked elements (see related topic)
Description Complete description of the risk. The description can have many Attachments (see related topic)
lines. The field will auto-extend.
Notes (see related topic)
Change History (see related topic)
Opportunity (1/2)
An opportunity can be seen as a positive risk. It is not a threat but the opportunity to have a positive impact to
the project.
Field Description
Status Actual status of the opportunity. May be linked to a workflow.
Change of the status can have several impacts :
automatically sending emails,
automatically update Handled, Done or Closed,
some fields may become mandatory (see related topic) .
Field Description
Responsible Resource who is responsible for the opportunity.
Id Unique Id for the opportunity. Reference is displayed after id.
Priority Expected priority to take into account this opportunity.
Project The project concerned by the opportunity. Mandatory.
Initial end date Initially expected end date of the opportunity.
Type Type of opportunity.
Planned end date Updated end date of the opportunity.
Name Short description of the opportunity. Mandatory.
Handled Flag to indicate that opportunity has been taken into account.
Creation date Creation date. Automatically generated on creation.
Issuer User who created the opportunity. Date of handling is saved.
This generally means that Responsible has been named.
Origin Origin of the opportunity. Can be any other item of the project.
Done Flag to indicate that opportunity has been treated.
Opportunity Description of the event that may trigger the opportunity. Date of completion is saved.
source
Closed Flag to indicate that opportunity is archived. opportunity will
Impact Description of the estimated positive impact on the project. not appear in lists any more, unless show closed is checked.
Severity Level of importance of the impact for the project. Result Complete description of the treatment of the opportunity.
The result can have many lines. The field will auto-extend.
Expected Evaluation of the estimated improvement, or positive impact, on
improvement the project of the opportunity. Field Description
Criticality Global evaluation level of impact the opportunity on the project. Linked elements (see related topic)
Description Complete description of the opportunity. The description can Attachments (see related topic)
have many lines. The field will auto-extend. Notes (see related topic)
Change History (see related topic)
Issue (1/2)
If the Risk Management Plan has been correctly managed, issues should always be occurring identified Risks.
Field Description
Status Actual status of the issue. May be linked to a workflow.
Change of the status can have several impacts :
Field Description automatically sending emails,
automatically update Handled, Done or Closed,
Id Unique Id for the issue. Reference is displayed after id.
some fields may become mandatory (see related topic) .
Project The project concerned by the issue. Mandatory.
Responsible Resource who is responsible for the treatment of the issue.
Type Type of issue.
Initial end date Initially expected end date of the issue.
Name Short description of the issue. Mandatory.
Creation date Creation date. Automatically generated on creation. Planned end Updated end date of the issue.
Can be changed. date
Issuer User who created the issue. Handled Flag to indicate that issue has been taken into account.
Can be changed (for instance if creator is not the issuer). Date of handling is saved.
This generally means that Responsible has been named.
Cause Description of the event that led to the issue.
Done Flag to indicate that issue has been treated.
Impact Description of the impact of the issue on the project. Date of completion is saved.
Criticality Level of importance of the impact for the project. Closed Flag to indicate that issue is archived. Issue will not appear in
Priority Priority requested to the treatment of the issue. lists any more, unless show closed is checked.
Description Complete description of the issue. The description can have many Result Complete description of the treatment of the issue.
lines. The field will auto-extend. The result can have many lines. The field will auto-extend.
Field Description
Linked elements (see related topic)
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Meeting (1/2)
Meeting items are stored to keep trace of important meetings during the project lifecycle :
Progress Meetings
Steering committees
Functional workshops
In fact, you should keep trace of every meeting where decisions are taken, or questions answered.
This will provide an easy way to find back when, where and why a decision has been taken.
After saving, the list is automatically formatted as receivers list, showing email (in Gmail like format) :
You can also directly enter an email address in the list, for external attendees.
They will receive the invitation in their calendar management tool (Outlook, Gmail, ).
Meeting (2/2)
Fields
Field Description
Parent activity Parent activity of the meeting in the WBS structure, under
which the meeting will be displayed in the Gantt planning.
Status Actual status of the meeting. May be linked to a workflow.
Change of the status can have several impacts :
Field Description
automatically sending emails,
Id Unique Id for the meeting. Reference is displayed after id. automatically update Handled, Done or Closed,
Project The project concerned by the meeting. Mandatory. some fields may become mandatory (see related topic) .
Meeting type Type of meeting. Responsible Resource who is responsible for the organization of the
meeting.
Meeting date Date of the meeting (initially expected date), including start and
end time. Handled Flag to indicate that meeting has been taken into account.
Date of handling is saved.
Name Name of the meeting. If not set, will automatically be set to
This generally means that Responsible has been named.
meeting type completed with meeting date.
Done Flag to indicate that meeting has been held.
Location Place (room or else) when meeting will stand.
Date of meeting is saved.
Assignment Resources can be assigned to meetings, exactly in the same way
as assignment to activities. Closed Flag to indicate that meeting is archived. Meeting will not
appear in lists any more, unless show closed is checked.
See activities for more information on assignment.
Other Extra list of persons attending (or expecting to attend) the Minutes Minutes of the meeting.
attendees meeting, in completion to Resource listed in Assignment table. You can enter here only a short summary of the minutes and
attach the full minutes as a file.
Duplicate email addresses with Assignment list will automatically
be removed
Field Description
Description Description of the meeting.
Linked elements (see related topic)
Can be used to store Agenda.
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Periodic Meeting (1/2)
Periodic meeting is a way to define some meetings that will occur on a regular basis.
Most fields fit meeting fields, but some information for meeting is not present for periodic meeting, such as
Minutes or Status. If is because these fields wont be set through periodic meeting definition, but must be set
directly on the meetings.
Field Description
Parent activity Parent activity of the periodic meeting in the WBS structure,
under which the periodic meeting will be displayed in the Gantt
planning. The meetings build from thing periodic meeting will
be grouped under this line.
Responsible Resource who is responsible for the organization of the
meeting.
Field Description Closed Flag to indicate that meeting is archived. Meeting will not
appear in lists any more, unless show closed is checked.
Id Unique Id for the periodic meeting.
Project The project concerned by the periodic meeting. Mandatory.
Meeting type Type of periodic meeting.
Name Name of the meeting. If not set, will automatically be set to
meeting type completed with meeting date.
Location Place (room or else) when meetings will stand.
Assignment Resources can be assigned to periodic meetings, exactly in the
same way as assignment to activities or to meetings. Field Description
See activities for more information on assignment.
Period Start date and End date or number of occurrences to define the
Other Extra list of persons attending (or expecting to attend) the range of the periodicity.
attendees meetings, in completion to Resource listed in Assignment table.
Time Start and end time for all the meetings.
Duplicate email addresses with Assignment list will automatically
be removed Periodicity Frequency of the meeting, on proposed bases (daily, weekly
Description Description of the meeting. monthly)
Can be used to store Agenda. Only on open Specify that meetings will not be set on off days.
days
Field Description
Linked elements (see related topic)
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Decision (1/2)
Decisions are stored to keep trace of important decisions, when, where and why the decision was taken.
You can link a decision to a meeting to rapidly find the minutes where the decision is described.
Decision (2/2)
Fields
Field Description
Linked elements (see related topic)
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Question (1/2)
The Questions can also afford an easy way to track questions sent and follow-up non-answered ones.
This will provide an easy way to find back when, who and precise description of the answer to a question.
Also keep in mind that some people will (consciously or not) be able to change their mind and uphold it has
always been their opinion
You can link a question to a meeting to rapidly find the minutes where the question was raised or answered.
Question (2/2)
Fields
Description Complete description of the question. The description can have Planned due Updated expected date for the answer to the question.
many lines. The field will auto-extend. date
Replier Name of the person who provided the answer.
Handled Flag to indicate that question has been taken into account.
Date of handling is saved.
This generally means that Responsible has been named.
Done Flag to indicate that question has been answered.
Date of answer is saved.
Closed Flag to indicate that question is archived. Question will not
Field Description appear in lists any more, unless show closed is checked.
Linked elements (see related topic) Response Complete description of the answer to the question.
The response can have many lines. The field will auto-extend.
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Emails
You can have a look at the list of the automatic emails sent (see related topic).
You will have all the information about the email, including the status showing whether the email was correctly
sent or not.
You can define some message that will be displayed on the today screen of users.
You can limit the display to some profile and/or project and/or user.
Field Description
Message Complete text of the message. The message can have many
lines. The field will auto-extend.
Field Description
The first line of the file must contain de name of the fields : look into the Model class : the
names are the same. Just click on specific help button to have help on fields.
You may or may not add an "id" column to the file :
- if column "id" exists and "id" is set for a line, the import will try to update the corresponding
element, and will fail if it does not exist
- if column "id" does not exists or if "id" is not set for a line, the import will create a new
element from the data.
In any case, columns with no data will not be updated : then you can update only one field on
an element. To clear a data, enter the value "NULL" (not case sensitive).
For columns corresponding to linked tables ("idXxxx"), you can indicate as the column name
either "idXxxx or Xxxx" (without "id") or the caption of the column (as displayed on
screens). If the value of the column is numeric, it is considered as the code of the item. If the
value of the column contains non numeric value, it is considered as name of the item, and the
code will be searched from the name.
Names of columns can contain spaces (to have better readability) : the spaces will be
removed to get the name of the column.
Insertion into "Planning" elements (activity, project), automatically inserts an element in the
table PlanningElement : the data of this table can be inserted into the import file (working
from version V1.3.0).
Import (2/2)
After selecting file format (CSV or XLSX) and file to import, you can Import Data.
You will then have a full report of the import :
Data that is not imported because not recognized as a field appear in grey text in the result table.
Data that are voluntarily not imported (because must be calculated) appear in blue text in the result table.
Imports can be automated : files placed on a defined directory will automatically be imported.
The automatic import process of a file just respect the standard import functionality. Refer to
it to have more information concerning file format.
Correctly imported files are move to a done sub folder of the import folder.
If an error occurs during import of a file, the full file is moved to error sub-folder of the
import folder, even if there is only one error over many other items correctly integrated.
You can get the result as log file and/or email summary.
Affectation
The affectation defines that a Resource, or Contact or User works on a given project, and so has visibility to
the given elements of the project (depending on habilitation).
Field Description
Id Unique Id for the affectation. Automatically generated on
creation.
Resource Affected Resource, or contact or User.
Or Contact When selecting one of the three, if the selected item is also of
Or User another king, then corresponding list is automatically selected.
For instance, if you select Resource R1 and that this resource is
also a User U1, then U1 will automatically be selected in User
list.
Project Project to affect to.
Rate (%) Affectation rate, in percent.
100% means a full time affectation.
Closed Flag to indicate that user is archived. User will not appear in lists
any more, unless show closed is checked.
Description Complete description of the user. The description can have many
lines. The field will auto-extend.
Field Description
Change History (see related topic)
User (1/2)
Field Description
Note that start and end dates of affectations have
Id Id of the affectation
direct impact on planning :
Project Project the resource is affected to.
planned work on tasks of the project will not start
before affectation start date Resource Name of the resource. Read only.
planned work on tasks of the project will not end Rate Rate (in %) of the affectation to the project.
It can be interesting to define all the informative data of the contact to be able to contact him when needed.
Field Description
Id Unique Id for the contact. Automatically generated on creation.
Name Name of the contact. Can contain first and last name.
This information will be displayed in lists.
Customer The Customer the contact belongs to (the contact is a person
into the organization of the customer).
Photo Photo of the contact. Click on + or photo frame to add an image
Is a resource Is this contact also a resource ?
Check this if the contact must also be assigned to activities and
be able to input real work . The contact will then also appear in
the Resources list.
Initials Initials of the contact
Is a user Is this contact also a user ?
Check this if the contact must connect to the application.
You must then define the user name, that can be the same as
the contact name or not, and the profile. The contact will then
also appear in the Users list.
Profile Profile of the user (see related topic)
User name User name (see related topic)
Mandatory if Is a user is checked.
Email address Email address of the contact.
Automatic emailing will use this address.
Field Description Phone Phone number of the contact. Informative data.
Address Full address of the contact. Mobile Mobile phone number of the contact. Informative data.
Fax Fax number of the contact. Informative data.
Closed Flag to indicate that contact is archived. Contact will not appear
in lists any more, unless show closed is checked.
Field Description
Description Complete description of the contact. The description can have
Change History (see related topic) many lines. The field will auto-extend.
Contact (2/2)
Affectations
It can be an internal entity, into the same enterprise, or a different enterprise, or the entity of an enterprise.
The customer defined here is not a person. Real persons into customer entity are called Contacts.
Field Description
Id Unique Id for the customer. Automatically generated on creation.
Customer Short name of the customer. Mandatory.
name
Customer Code of the customer. Informative data.
code
Delay for Delay for payment (in days) that can be displayed in the bill. Field Description
payment
Address Full address of the customer.
Tax (%) Tax rates that are applied to bill amounts for this customer.
Projects List of the projects of the customer.
Closed Flag to indicate that customer is archived. Customer will not
Contacts List of the contacts known in the entity of the customer.
appear in lists any more, unless show closed is checked.
Description Complete description of the customer. The description can have
many lines. The field will auto-extend.
Field Description
Change History (see related topic)
Recipient
Id Unique Id for the recipient. Automatically generated on creation. Designation Full name of the recipient as it appears in the address.
Name Name of the recipient. Mandatory. Street Street name, including street number.
The actual version of the tool does not use much of team notion.
Id Unique Id for the team. Automatically generated on creation. Team List of the resources member of the team.
members
Name Name of the team.
Closed Flag to indicate that team is archived. Team will not appear in It is possible to directly affect every team member to a
lists any more, unless show closed is checked.
project, using the corresponding button.
Description Complete description of the team. The description can have
many lines. The field will auto-extend.
Field Description
Project Project the team members are affected to.
Resource Not needed here. Read only.
Rate Rate (in %) of the affectations to the project.
Field Description Closed Not needed here. Read only.
Change History (see related topic)
Product
A product is any element delivered by the project. For IT/IS Projects, products are generally Applications.
Field Description
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Version
Field Description
Id Unique Id for the version. Automatically generated on creation.
Product The product on which the version applies.
Name Name of the version.
Prime The contact, into customer organization, who will be responsible
contractor for the version delivery. Can be different from Product prime
contractor. Field Description
Responsible Resource responsible of the version.
Project Project linked to the version.
Creation date Creation date. Automatically generated on creation.
Version Current version. Read only.
Can be changed.
Start date Start date for validity of the link
Entry into Initial, planned and real entry into service date of the version.
service Done is checked when real is set. End date End date for validity of the link
End date Initial, planned and real end dates of the version. Done is Closed Flag to indicate that link is not active any more, without deleting it.
checked when real is set, corresponding to closed version.
Description Complete description of the version. The description can have Field Description
many lines. The field will auto-extend.
Attachments (see related topic)
Notes (see related topic)
Change History (see related topic)
Context
Contexts are initially set to be able to define contexts for IT Projects, for three context types :
Environment
Operating System
Browser
They can be changed to be adapted to any kind of project.
Field Description
Id Unique Id for the context. Automatically generated on creation.
Context type One on the three context type.
List is fixed.
Captions are translated and so can be changed in language file (see related topic)
Name Name of the context
Sort order Number to define order of display in lists
Closed Flag to indicate that context is archived. Context will not appear in lists any more,
unless show closed is checked.
Field Description
Change History (see related topic)
Calendar (1/2)
A calendar of selected year (see above) is displayed to give a global overview of the exceptions existing :
in blue exception off days,
in red exception open days,
in bold current day.
Just click on one day in the calendar to switch between off and open day.
Document Directory
Field Description
Field Description
The quality is a manual indicator for the conformity of a project to quality processes.
It defines in a visual way the global conformity of the project.
Field Description
The trend is a manual indicator for the global trend of project health.
It defines in a visual way the health trend of the project.
It is displayed on Today screen, for each project.
Field Description
Field Description
The risk severity designs the level of impact the risk may have to the product.
Field Description
The ticket urgency is an element given by the requestor to indicate the quickness of treatment needed for
the ticket.
Field Description
Field Description
Field Description
Field Description
Field Description
The predefined note set the possibility to define some predefined texts for notes.
When some predefined notes are defined for an element and / or type a list will appear on note creation.
Selecting an item in the list will automatically fill in the note text field.
Field Description
A workflow defines the possibility to go from one status to another one, and who (depending on profile) can do
this operation for each status.
Once defined, a workflow can be linked to any type of any tem.
Field Description
The habilitation table helps defining who can move from one status to another one.
Each line correspond to the status from which you want to be able to move.
Each column correspond to the status to which you want to be able to go.
It is not possible to go from one status to itself (these cells are blank).
Just check the profile (or all) who is allowed to pass from one status to the other.
In the upper example, anyone can move an item from recorded to assigned and from recorded to
cancelled.
No one can move an item from qualified status to any other status. In this case, pay attention that it must
never be possible to move an item to qualified status, because it will not be possible to leave this status.
Mails on event
The application is able to automatically send mails on event such as status change or responsible change.
This must be defined for each type of element, and each new status or other event.
Field Description
When a user receives an email from ProjeQtOr, he may reply to the email.
This message (up to double blank lines) will be included in the notes of the corresponding item.
For this to run correctly :
IMAP account to be checked must be correctly configured in the global parameters screen
The reply message will be interpreted to retrieve item to update and reply message.
Some rules must be respected when replying to email :
1)Include original message (it will be used to retrieve item to update)
2)End reply message with 2 blank lines : it will be interpreted as end of message to be included as note
For security reasons, only reply from sender whos email is know as email for a resource, a contact or a user
will be taken into account.
This will avoid to store notes from spam mails.
Delay for Ticket
It is possible to define default delay for tickets, for each ticket type and each urgency of ticket.
On creation, due date will automatically be calculated as creation date + delay.
Field Description
Field Description
On indicatorable items, you may see a small incon on top left of detail of the item.
Just move the mouse over the icon to display which indicator has been raised.
Checklist Definition
Field Description
(multi selection is then possible). Exclusive Are the choices exclusive (select one will unselect others)
Checklist lines are displayed how they will appear in checklist :
Project type
Field Description
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type
Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Activity type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Milestone type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Quotation type
Quotation type is a way to define the way the concerned activity should be billed.
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference.
this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type
Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Closed Flag to indicate that type is archived. Lock handled Defines whether the handled check is locked or not for items of
this type.
Description Description of the type
If locked, this flag can only be update through status change.
Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the closed check is locked or not for items of
this type.
If locked, this flag can only be update through status change.
Lock canceled Defines whether the cancelled check is locked or not for items of
this type.
If locked, this flag can only be update through status change.
Order type
Order type is a way to define the way the activity references by the order will be billed.
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference.
this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type
Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Closed Flag to indicate that type is archived. Lock handled Defines whether the handled check is locked or not for items of
this type.
Description Description of the type
If locked, this flag can only be update through status change.
Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the closed check is locked or not for items of
this type.
If locked, this flag can only be update through status change.
Lock canceled Defines whether the cancelled check is locked or not for items of
this type.
If locked, this flag can only be update through status change.
Individual expense type
Individual expense type is a way to define common behavior on group of individual expense.
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Lock closed Defines whether the done check is locked or not for items of this
Workflow Defined the workflow ruling status change for items of this type
type.
Sort order Number to define order of display in lists If locked, this flag can only be update through status change.
Project expense type is a way to define common behavior on group of project expense.
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Lock closed Defines whether the done check is locked or not for items of this
Workflow Defined the workflow ruling status change for items of this type
type.
Sort order Number to define order of display in lists If locked, this flag can only be update through status change.
Expense detail type is a way to define common behavior and calculation mode on group of expense details.
Field Description
Value / unit 3 lines to define calculation mode for the detail type.
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 value.
Closed Flag to indicate that type is archived.
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Lock done Defines whether the done check is locked or not for items of this
Code Code of the type. Used to calculate reference.
type.
Workflow Defined the workflow ruling status change for items of this type If locked, this flag can only be update through status change.
Sort order Number to define order of display in lists Lock closed Defines whether the done check is locked or not for items of this
type.
Closed Flag to indicate that type is archived. If locked, this flag can only be update through status change.
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Opportunity type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Action type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Issue type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Meeting type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Decision type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Question type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Message type
Message type is a way to define common behavior on group of messages (appearing on today screen).
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Color Display color for messages of this type
Sort order Number to define order of display in lists
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Code Code of the type. Used to calculate reference.
Workflow Defined the workflow ruling status change for items of this type
Sort order Number to define order of display in lists
Context type is defining a fixed list of environmental context to describe ticket or test case.
Only three context types exist, corresponding to the three selectable fields in ticket or test case.
Only the name of the context types can be changed.
No new context type can be added.
No context type can be deleted.
Field Description
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Test case type
Test case type is a way to define common behavior on group of test cases.
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Test session type
Test session type is a way to define common behavior on group of test sessions.
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Responsible Defines whether the responsible is mandatory or not for items of
Code Code of the type. Used to calculate reference. this type when the handled status is on.
Workflow Defined the workflow ruling status change for items of this type Result Defines whether the result is mandatory or not for items of this
Sort order Number to define order of display in lists type when the done status is on.
Lock handled Defines whether the handled check is locked or not for items of
Closed Flag to indicate that type is archived. this type.
If locked, this flag can only be update through status change.
Description Description of the type Lock done Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Lock closed Defines whether the done check is locked or not for items of this
type.
If locked, this flag can only be update through status change.
Customer type
Id Unique Id for the type. Automatically generated on creation. Description Defines whether the description is mandatory or not for items of
this type
Name Name of the type.
Sort order Number to define order of display in lists
Field Description
The access mode defines a combination of rights to read, created, update or delete items.
Each access is defined as scope of visible and/or updatable elements, that can be :
No element : no element is visible and/or updatable
Own elements : only the elements created by the user
Elements he is responsible for : only the elements the user is responsible for
Elements of own project : only the elements of the projects the user/resource is affected to
All elements on all projects : all elements, whatever the project
Field Description
Access to forms defines for each screen the profiles of users that can access to the screen.
Users belonging to a profile not checked for a screen will not see the corresponding menu.
Access to reports
Access to reports defines for each report the profiles of users that can access to the report.
Users belonging to a profile not checked for a report will not see the corresponding report in the report list.
Access mode to data
Access mode defines for each Project dependent screen the access mode (scope of visibility and
updatability) for each profile.
Specific access mode (1/2)
Real work allocation access mode defines the visibility a user can have on real work allocation, and define
which profile can validate weekly work for resources.
It is mostly used to define profiles who will be able to see and/or update real work for other users and
validate their work follow-up. In most case, it is devoted to Project Leader.
Work and cost visibility defines for each profile the scope of visibility of work and cost data.
Assignment management defines the visibility and possibility to edit assignments (on activities or else)
Specific access mode (2/2)
Display of combo detail button defines for each profile whether a button will be displayed or not, facing
every combo list box. Through this button, it is possible to select item and/or create new item. This button may
also be hidden depending on access right (if the user has no read right to corresponding elements).
Access to checklist defines visibility or not to the checklist (if defined)
Planning calculation defines for each profile the ability to calculate planning or not.
Unlock items defines for each profile the ability to unlock any document or requirement.
Otherwise, each user can only unlock the documents and requirements locked by himself.
Administration
Moving the mouse over the caption of a parameter will display a tooltip with more description about the
parameter
Definition of the unit (days or hours) for real work allocation and
for all work data. Remember that data is always stored in days. If
both values are different, rounding errors may occur.
Attention : duration will always be displayed in days, whatever
the workload unit.
Moving the mouse over the caption of a parameter will display a tooltip with more description about the
parameter
Moving the mouse over the caption of a parameter will display a tooltip with more description about the
parameter
Miscellaneous parameters :
Auto check (or not) for existing new version of the tool (only
administrator is informed)
Separator for CSV files (on export and export)
Memory limit for PDF generation
Global parameters (4/7)
Moving the mouse over the caption of a parameter will display a tooltip with more description about the
parameter
Moving the mouse over the caption of a parameter will display a tooltip with more description about the
parameter
Parameters for the Cron process.
This defined frequency for these automatic functions.
It will manage :
alert generation : frequency for recalculation of indicators values
check alert : frequency for client side browser to check if alert
has to be displayed
import : automatic import parameters
Moving the mouse over the caption of a parameter will display a tooltip with more description about the
parameter
You can select the method just adding $paramMailerType in your parameters.php file :
$paramMailerType=mail using php mail function
$paramMailerType=socket using specific socket connection
$paramMailerType=phpmailer using PHPMailer library
Global parameters (7/7)
Moving the mouse over the caption of a parameter will display a tooltip with more description about the
parameter
NB: don't forget to save your lang.xls file and identify your changes (for instance using vers. column) because
you will have to re-apply them after each new version deployment.
Automatic emailing
You changed the status of a ticket and the tool replied "Item updated email sent".
But what contained that email ? And why did you not receive this email ?
Just go to Menu "Tools" "Sent emails" to see the content of the email !
Youll see who was addressee of the email.
If youre not in the list, just check with your admin, its a question of email parameters.
But this is another story
ProjeQtOr provides an API to interact with its elements. It is provided as REST Web Service.
It is possible to read (method GET), create (methods PUT, POST), update (methods PUT, POST) and delete
(method DELETE) elements.
First, the API must be enabled : for security reasons it is not enabled by default.
Generate a .htpasswd file (see related topics on the net on how to do this)
A template is provided in /api/.htpasswd, referring to user projeqtor, password projeqtor.
It is provided only for test purpose.
Do not use it on a production environment as it would expose all your data.
Update .htaccess file to specify location of your .htpasswd file :
AuthUserFile "/pathToFile/.htpasswd
Default location is Apache directory.
Use of API :
Since V4.4, user used (defined in .htpassword) must exist as a User in the database.
Then, access rights (read, create, update, delete) to the access defined for this user.
This allows you to provide some access to external users and control the visibility they get on your
data
Available methods are GET (read), PUT (create, update), POST (create, update) and DELETE
(delete)
For PUT, PUSH and DELETE methods, data must be encrypted with AES-256 algorythm, with key
as the API key defined for the user. Admin must provide this API Key to the API consumer.
You can use AESCRT library provided in /external directory for the encryption.
PUT and PUSH methods are similar and can both be used to create or update elements.
Difference is only in the way to send data : as a Post array for POST, as a file for PUT.
DELETE method requires data, formatted as for a PUT, but only id is required.
For PUT, POST and DELETE, you can provide :
a single item : {id:1, }
a list of items : {identified:id, items:[{id:1, }, {id:2, }]}
Json format retrieved from GET can be used for PUT, POST and DELETE.
API
GET http://myserver/api/{object class}/all The complete description, in Json format, of all the objects
Ex : http://myserver/api/Project/all of the given class
GET http://myserver/api/{object class}/filter/{filter id} The complete description, in Json format, of all the objects
Ex : http://myserver/api/Project/filter/1 of the given class corresponding to the given stored filter
id of the filter can be retrieved when saving filter
Using filter of a different class may lead to unexpected
results.
GET http://myserver/api/{object class}/search/{crit1}/{critN} The complete description, in Json format, of all the objects
Ex : of the given class corresponding to the given criteria.
http://myserver/api/Activity/search/idProject=1/name like you can provide as many criteria as you wish, they will
%error% be included in where clause with AND operator.
unlike example, criteria must be url encoded (use PHP
urlencode() function for instance)
GET http://myserver/api/{object class}/updated/{start date}/ The complete description, in Json format, of all the objects
{end date} updated between start date en end date
Ex : http://myserver/api/Project/updated/ Date format is YYYYMMDDHHMNSS
20130101000000/20131231235959 Date >= start date and Date < end date
Here is an example of PHP code calling the API for GET request (read) :
$fullUrl="http://myserver/api/Ticket/list/all";
$curl = curl_init($fullUrl);
curl_setopt($curl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
curl_setopt($curl, CURLOPT_USERPWD, "projeqtor:projeqtor");
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
$curl_response = curl_exec($curl);
echo $curl_response;
curl_close($curl);
This request lists all Tickets
Here is an example of PHP code calling the API for DELETE request (create, update):
$fullUrl="http://myserver/api/Ticket";
$data='{"id":"1"}';
$data=AesCtr::encrypt($data, 'ApiKeyForUserProjeqtor', 256);
$curl = curl_init($fullUrl);
curl_setopt($curl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
curl_setopt($curl, CURLOPT_USERPWD, "projeqtor:projeqtor");
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($curl, CURLOPT_CUSTOMREQUEST, "DELETE");
curl_setopt($curl, CURLOPT_POST, true);
curl_setopt($curl, CURLOPT_POSTFIELDS, $data);
$curl_response = curl_exec($curl);
echo $curl_response;
curl_close($curl);
This request deletes Ticket #1
API
Here is an example of PHP code calling the API for PUT and POST request (create, update):
$fullUrl="http://myserver/api/Ticket";
$data='{"id":"1", "name":"name to be changed for Ticket 1"}';
$data=AesCtr::encrypt($data, 'ApiKeyForUserProjeqtor', 256);
$curl = curl_init($fullUrl);
curl_setopt($curl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
curl_setopt($curl, CURLOPT_USERPWD, "projeqtor:projeqtor");
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($curl, CURLOPT_CUSTOMREQUEST, "PUT");
curl_setopt($curl, CURLOPT_POST, true);
curl_setopt($curl, CURLOPT_POSTFIELDS, $data);
$curl_response = curl_exec($curl);
echo $curl_response;
curl_close($curl);
$fullUrl="http://myserver/api/Ticket";
$data='{"id":"1", "name":"name to be changed for Ticket 1"}';
$data=AesCtr::encrypt($data, 'ApiKeyForUserProjeqtor', 256);
$curl = curl_init($fullUrl);
curl_setopt($curl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
curl_setopt($curl, CURLOPT_USERPWD, "projeqtor:projeqtor");
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($curl, CURLOPT_CUSTOMREQUEST, "POST");
curl_setopt($curl, CURLOPT_POST, true);
curl_setopt($curl, CURLOPT_POSTFIELDS, array('data'=>$data));
$curl_response = curl_exec($curl);
echo $curl_response;
curl_close($curl);
These requests update name of Ticket #1
Linked elements
It can only be deleted with icon. Id Unique Id for the attachment. Automatically generated on
creation. Id are shared for all projects and all attachments.
Only the user who created the attachment can delete it.
Size Size of the file.
Click on icon to download the attached file.
Type Mime type of the file. Displayed as an icon.
Click on icon to access the hyperlink page.
If file is an image, will be displayed as thumb of the image,
Attachment visibility can be : and click on the thumb will display full size image.
public : visible to anyone File File name.
team : visible to every member of the creators team
Date Date of creation of the attachment.
private : visible only to creator
User Name of the user who attached the file.
Attached files are stored on server side, on a place specified by the administrator on parameters.
Files can be directly attached using drag & drop move into the devoted zone.
Notes
To add a note, just click on the icon. Creation date is displayed straight.
Last modification date is displayed in italic.
A note pop-up will appear :
User Name of the user who created the note.
Type Mime type of the file.
Note Text of the note.
If the text of the note contains an url, it will be displayed as a
clickable hyperlink.
They are stored and displayed on each item. Date Date of change operation.
User Name of the user who operated the change.
On creation, just an insert operation is stored, Operation The operation on the item (insert or update)
not all the initial values on creation. Data The field modified.
Value before The value of the field before the update.
Value after The value of the field after the update.
Change history section can be folded or unfolded, clicking on the section title.
Each user can change on user parameters the default display of the section (folded or not) or even
select to hide this section.
Backup / Restore
You should also always backup your Data before any application upgrade... in case of ...
Hints :
be sure to use UTF-8 charset when exporting / importing
[CTRL]+S
you cannot import into a full Database (with existing Data) :
either you truncate the tables before import
(you must then assure to import Data into a structure of the same version of application !)
or you drop the tables before import
or you export data including Drop tables
regularly test your back-up files, trying to restore it on an empty Database
(many times backup are never tested, and can not be imported when needed...)
[CTRL]+S
Last words
Hofstader's Law
"It always takes longer than you expect, even if you take Hofstadter's Law into
account"
Murphy's Law
"Whatever can go wrong will go wrong"
"... and at the worst possible time, in the worst possible way."
http://www.projeqtor.org
You can also access to the track Database (running as a ProjeQtOr instance) to see details of
changes as tickets.