Documente Academic
Documente Profesional
Documente Cultură
Functional (1/5)
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.
Risk Management Plan
Risk follow-up, with complete description of risks and criticality enlightening.
Issue follow-up, to track Project issues when risks occur.
Opportunities management
Links management, between Actions, Issues and Risks, or any other item.
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.
Controls and automations
Workflow definition, controlling status change.
Automatic email generation on status change and other event (note add, ).
Definition of delays for tickets.
Calculation of indicators, based on target values (dates, work, ).
Automatic alerts based on indicators value.
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.
Requirement & Tests management
Definition of tests cases, including pre-requisite and expected result.
Definition of test sessions, listing test cases to run, with result status.
Definition of requirements, linked to tests cases, with test case coverage summary.
Parameters and lists of values
Every parameter, every list of values may be changed through a devoted screen.
Every element is linked to a type, defining some mandatory data or other GUI behavior.
Functional (5/5)
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 :
ZEND Server 4.0.5 Community Edition [Apache V2.2.12, MySQL 5.1.35, PHP V5.2.10]
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
When you first log in, normal process should be :
configuration screen is displayed
you fulfill data corresponding to your environment
you then click on "OK" button
a spinner is displayed
the spinner disappears : at that moment, you should see a message and a new
"Continue" button below the "OK" button
you click on the "Continue" button
screen changes to Logon screen
you enter default login : admin/admin and click "OK" button
spinner is displayed : this step may take a certain time (about 1 minute) because all the
database structure is created
spinner disappears and a short message indicates result of database creation (detail of
this step is written in log file)
click again on "OK" and you're in !
If all of this do not work, try this solution :
get /tool/parameters.php file
manually update this file with your own parameters
create a new file : /tool/parametersLocation.php containing:
<?php $parametersLocation = "parameters.php";
You can move /tool/parametrers.php, then you just have to indicate its full way in
/tool/parametersLocation.php.
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.
Caption
Description
Variable name
Database type
$paramDbType
$paramDbHost
Database user to
connect
$paramDbUser
Database password
for user
$paramDbPassword
Database schema
name
$paramDbName
Name to be
displayed
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)
Caption
Description
Variable name
eMail address of
sender
$paramMailSender
eMail address to
reply to
The email address used to define the reply to for mailing function.
eMail of
administrator
SMTP Server
SMTP Port
$paramMailSmtpServer
[New in V1.2.0]
$paramMailSmtpPort
[New in V1.2.0]
Sendmail program
path
$paramMailSendmailPath
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)
Caption
Description
Variable name
$paramDefaultPassword
Default locale to be
used on i18n
$paramDefaultLocale
$paramDefaultTimezone
Tag to indicate that screens will appear in a fading motion, to avoid flickering
screens.
$paramFadeLoadingMode
$paramIconSize
$defaultTheme
Possible values are 'blue', 'red', 'green', 'orange', 'grey', 'white' or 'random'
for randomly selected (default is 'blue).
[New in V1.3.0]
Possible values are '16' for small icons, '22' for medium icons, '32' for big
icons (default is '22).
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)
Caption
Description
Variable name
Directory to store
Attachments
Directory where attached files will be stored. Can be any valid directory.
$paramAttachementDirectory
Max file size for attached files. Size is in bytes (1024 * 1024 * MB).
$paramAttachementMaxSize
$paramMemoryLimitForPDF
[New in V1.6.1]
$logFile
$logLevel
Possible values are '4' for script tracing, '3' for debug, '2' for general trace,
'1' for error trace, '0' for none (default value is '2).
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)
Caption
Description
Variable name
Currency
$currency
Currency position
$currencyPosition
Stored as
$parametersLocation in
parametersLocation.php file
$paramLdap_allow_login
[New in V1.8.0]
Ldap Port
Ldap Port .
Default is 389.
Ldap version
Ldap version .
Possible values are 2 or 3.
$paramLdap_base_dn
[New in V1.8.0]
$paramLdap_host
[New in V1.8.0]
$paramLdap_port
[New in V1.8.0]
$paramLdap_version
[New in V1.8.0]
$paramLdap_search_user
[New in V1.8.0]
$paramLdap_search_pass
[New in V1.8.0]
Ldap filter
Ldap filter to find used name . Must include %USERNAME% that will be
replaced be the login user name.
$paramLdap_user_filter
[New in V1.8.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.
Generality
Splitter
List
area
Menu
area
Splitter
Splitter
Detail
area
Message
and
hyperlink
area
Info bar
Menu
Quick Menu
List
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
Click on the csv export
Filters
Filters
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.
Detail
The Detail area present the detail of the selected in the list.
Click on
to create new item,
to save the changes,
to copy the current item,
to cancel ongoing changes,
and
to send detail of item by email.
Some buttons are not clickable when change are ongoing :
or
to get a printable version of the detail,
to delete the item,
to refresh the display
,
to edit and
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.
to delete.
Combo Detail
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
Themes (1/2)
Users can select colors Theme to display the interface.
Just go to Menu "Parameters" "Users parameters", and select the new theme in the
"theme" select list.
New theme is automatically applied when selected.
Just save parameters to retrieve this theme on each new connection.
Administrator defines on parameters file a default Themes that will be applied on Login screen
and up until the users selects a specific theme.
The random Theme is not really a Theme, it is a functionality to randomly select a Theme on
each new connection.
Default
Light
Dark
Fire
Forest
Earth
Water
Wine
Default
Light
Contrasted
ProjeQtOr
ProjeQtOr
ProjectOr RIA
(old style)
Themes (2/2)
Light
Dark
Contrasted
Blue
Red
Green
Orange
Black & White
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.
Every item has a unique Id, automatically generated on creation.
Id is chronologically affected, for all kind of items (Activity, Ticket).
Id is shared for all projects and all types (i.e. incident) of the same kind items (i.e. Ticket).
Reference is displayed after id, automatically generated on creation.
Reference depends on defined format in Global parameters screen.
Default format defines an numbering specific for each project and each type of items.
Create
Create
Create
Create
Create
Create
...
Id
Id
Id
Id
Id
Id
#1
#2
#3
#4
#1
#2
Reference
Reference
Reference
Reference
Reference
Reference
PRO1-INC-0001
PRO2-INC-0001
PRO1-ANO-0001
PRO1-INC-0002
PRO1-EVO-0001
PRO2-EVO-0001
Update specificity
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.
Items with existing dependencies can not be deleted.
Examples :
You can not delete an activity if a resource is assigned to it.
You can not delete an assignment is real work has been entered (imputation).
You can not delete a project with existing items.
Copy specificity
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 (subprojects, 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
On most items, it is possible to send an informative email to defined recipients list.
Just click on button
to select recipients and message of email.
requestor
issuer
responsible
project team
project leader
project manager
assigned resource
other
message
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).
the User defined as Issuer on current item
the Resource defined as responsible on current item
all Resources affected to the Project of the current item
the Resource(s) affected to the Project of the current item, with a Project Leader profile (profile with code =
PL)
the User defined as manager on the Project of the current item
all Resources assigned to the current item (disabled for not assignable items)
provides an extra field to manually enter email addresses
the message that will be included in the body of the email, in addition to complete description of item
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
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.
The user just has to check information corresponding to the situation.
When done, the user name and checked date is recorded, and can be displayed moving the icon
over the
picture.
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.
The fields are presented in the order as they appear in
the item description.
You can easily check or uncheck all fields to export.
You can also easily restrict selected fields to the ones
that are actually displayed in the list.
For fields that reference another item (displayed as lists
in the item description), you can select to export either
the id or the clear name of the referenced item.
Today (1/2)
The Today screen is the first to be displayed on each connection.
It is divided in several parts. Each part can be folded/unfolded with a click on the header.
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.
Today (2/2)
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)
Project is the main entity of ProjeQtOr.
It is also the top level of visibility, depending on profiles.
You can define some profiles, some will have visibility to all projects, others only to projects they are affected
to.
You can also define sub-projects of a project. Then, project may not be real projects, but just organizational
breakdown corresponding to the organization.
This splitting can be functional :
Project X
Project X
Product V1
or organizational :
Project X
Product V2
Project X
Product V3
Project X
Project X
Product V1
Maintenance
Project X
Product V1
Evolutions
Project X
Product V1
Bug Fixing
Project X
Product V2
Development
Project X V1 can be
shared with a large scope
of users, while others will
be restricted to internal
team.
Project X
Project X Product V1
Project X Product V2
Project X Product V3
Project X
Project X
Project
Project
Bug.
Project X
Product V1 Maint.
X Product V1 Evo.
X Product V1
Product V2 Dev.
Fields
Field
Description
Attachments
Notes
Change History
Project (2/5)
Field
Description
Id
Name
Type
Customer
Bill contact
Billing contact.
Project code
Contract code
Is sub-project of
Sponsor
Manager
Color
Status
Health status
Quality level
Trend
Overall progress
Fix planning
Done
Closed
Cancelled
Description
Project (3/5)
Field
Description
Sub projects
Description
Id
Id of the affectation
Project
Resource
Rate
Closed
Description
Project
Version
Start date
End date
Closed
Project (4/5)
Progress
The progress information will impact Planning calculation, and is also calculated during Planning calculation.
(see related topic)
Field
Description
Requested duration
Validated duration
Committed work / cost : total work / cost of the project should not be more.
Sum of all the assigned work / cost for the assignments on the project. Read only.
Calculated start date, taking into account all the constraints (see related topic). Read only.
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)
Calculated total work / cost needed to complete the task. Read only. planned = real + left
Date of the first real work input entered by an resource on the real work allocation screen. Read only.
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.
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 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.
Dependencies
Project (5/5)
Field
Description
Click on
to delete the corresponding
dependency.
Type
Id
Name
Status
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.
Click on the name of a predecessor or successor will directly move to it.
Document (1/4)
A document is a referential element that give description to a product or a project.
A global definition of a document refers to any kind of information.
This means that a document can be a file (text document, image, ) or any non digital item (paper mail, fax,
), or non file digital item (email, ).
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.
The Document item describes general information about the document.
The file is not stored at this level.
A document can evolve and a new file is generated at each evolution.
So files are stored at document version level.
A document can evolve following 4 ways defined as versioning type :
Evolutive : Version is a standard Vx.y format.
It is the most commonly used versioning type.
Major updates increase x and reset y to zero.
Minor updates increase y.
Chronological : Version is a date.
This versioning type is commonly used for periodical documents
For instance : weekly boards.
Sequential :
Version is a sequential number.
This versioning type is commonly used for recurring documents
For instance : Meeting reviews.
Custom :
Version is manually set.
This versioning type is commonly used for external documents, when version is not managed by the tool, or
when the format cannot fit any other versioning type.
Fields
Document (2/4)
Field
Description
Id
Document
reference
Project
Product
Directory
Type
Type of document.
Name
Author
Field
Description
Linked elements
Change History
Closed
Cancelled
Field
Description
Lock / Unlock
this
document
Locked
Locked by
Locked since
Date and time when document was locked (if locked). Read only.
Versions
Document (3/4)
Field
Description
Versioning
type
Last version
Status
Description
File
Last version
Update
New version
Date
Status
Is a
reference
Description
Approvers
Document (4/4)
Field
Description
Id
Name
Status
It is also possible to send a reminder email to all the approvers who have not yet approved the document.
Ticket (1/3)
A ticket is a kind of task that can not be unitarily planned.
It is generally a short time activity for a single ticket, that is interesting to follow unitarily to give a feedback to
the issuer or to keep trace of result.
It can be globally planned as a general activity, but not unitarily.
For instance, bugs should be managed through tickets :
you can not plan bugs before they are registered,
you must be able to give a feedback on each bug,
you can (or at least should) globally plan bug fixing activity.
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.
Fields
Ticket (2/3)
Field
Description
Id
Project
Ticket type
Type of ticket.
Name
External
reference
Urgency
Creation
date/time
Issuer
Can be changed.
Can be changed (for instance if creator is not the issuer).
Requestor
Origin
Duplicate
ticket
Context
Original
version
Description
Ticket (3/3)
Fields
Field
Description
Planning
Activity
Status
Responsible
Criticality
Priority
Actual due
date
Estimated
work
Real work
Left work
Handled
Done
Closed
Field
Description
Cancelled
Linked elements
Target version
Attachments
The target version of the product that will deliver the object of
the ticket.
Notes
Result
Change History
Fields
Description
Id
Project
Ticket type
Name
Urgency
Creation
date/time
Issuer
Context
Description
Fields
Description
Status
Field
Description
Linked elements
Attachments
Notes
Change History
Responsible
Due date
Handled
Done
Closed
Cancelled
Target version
The target version of the product that will deliver the object of
the ticket.
Result
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,
Fields
Activity (2/5)
Field
Description
Field
Description
Parent Activity
Id
Status
Project
Activity type
Type of activity.
Name
External
reference
Creation date
Done
Can be changed.
Issuer
Requestor
Origin
Description
Field
Description
Linked elements
Attachments
Notes
Change History
Cancelled
Target version
The target version of the product that will deliver the object of
the activity.
Result
Assignments
Activity (3/5)
Click on
to delete the assignment. If real work
exists for an assignment, it can not be deleted.
It is possible to assign several times the same
resource to an activity. It can for instance be used to
add extra work without modifying initial assignment.
Click on the resource name will directly move to the
resource.
Field
Description
Resource
Function
Cost
Rate
Assigned
work
Real work
Left work
Planned work
Comments
Activity (4/5)
Progress
The progress information will impact Planning calculation, and is also calculated during Planning calculation.
Field
Description
Requested duration
Validated duration
Committed work / cost : total work / cost of the activity should not be more.
Sum of all the assigned work / cost for the assignments on the activity. Read only.
Calculated start date, taking into account all the constraints (see related topic). Read only.
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)
Calculated total work / cost needed to complete the task. Read only. planned = real + left
Date of the first real work input entered by an resource on the real work allocation screen. Read only.
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.
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 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.
Dependencies
Activity (5/5)
Field
Description
Type
Id
Name
Status
Click on
to delete the corresponding
dependency.
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.
Click on the name of a predecessor or successor will directly move to it.
Milestone (1/4)
A Milestone is a flag in the planning, to point out key dates.
Milestones are commonly used to check delivery dates.
They can also by used to highlight transition from one phase to the following one.
Opposite to Activities, Milestones have no duration and no work.
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.
Fields
Milestone (2/4)
Description
Field
Description
Id
Parent Activity
Project
Status
Milestone
type
Type of milestone.
Name
Creation date
Field
Issuer
Can be changed.
Responsible
Handled
Done
Description
Field
Description
Linked elements
Attachments
Notes
Change History
Cancelled
Target version
The target version of the product that will deliver the object of
the milestone.
Result
Progress
Milestone (3/4)
Field
Description
Calculated end date, taking into account all the constraints (see related topic). Read only.
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.
Dependencies
Milestone (4/4)
Field
Description
Type
Id
Name
Status
Action (1/2)
An action is a task or activity that is set-up in order to :
- reduce the likelihood of a risk
- or reduce the impact of a risk
- or solve an issue
- or build a post-meeting action plan
- or just define a to do list.
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.
Fields
Action (2/2)
Field
Description
Id
Field
Description
Project
Status
action type
Type of action.
Name
Creation date
Issuer
Priority
Description
Planned due
date
Handled
Done
Field
Description
Linked elements
Attachments
Notes
Change History
Closed
Cancelled
Efficiency
Result
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)
Planning is displayed as a Gantt chart, showing dependencies between tasks.
can
can
can
can
can
You can
of tasks
You can
You can
change the scale to have a daily, weekly or monthly view of the chart.
select to show tasks WBS before the names.
select to show resource name or initials (depending on parameter) on right on tasks.
change the starting
or ending
date to display the chart.
also choose to save these dates
to retrieve the same display on every connection.
select the columns displayed on the left part of the chart, except for the name
(always displayed).
reorder columns with drag & drop on the handle in the selection list.
directly create a Project or an Activity or a Milestone using the
create button.
Planning (2/5)
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)
Planning is calculated as simply as possible.
This means that no complex algorithm, with high level mathematic formula, is involved.
The principle is simply to reproduce what you could do on your own, with a simple Excel
sheet, but automatically.
Planning is Cross-Project, through affectation rate on the projects.
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 has a capacity
Most of the time Capacity = 1 FTE (1 full time equivalent), but it may be more (if the resource is not a person
but a team) or less (if the person work only partial time).
A resource is affected to a project, at a certain rate
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)
A resource is assigned to an activity, at a certain rate
By default, assignment rate is 100%. But it may be less. This means that planning will keep some
availability for other tasks.
Assignment capacity is controlled on a daily basis. This means that planning for an activity will not be more
than (Resource Capacity) x (Resource assignment rate) for a given day.
An activity has dependencies
An activity will always be planned after its predecessors (and this is recursive).
An activity has a priority and planning mode
Activity with lower priority will be planned first (after taking account of dependencies).
Default priority is 500 (medium).
Possible Planning modes are :
As soon as possible: Default planning behavior. Task is planned to finish as soon as possible
Work together: Same as above, but when 2 (or more) resources are assigned, planning tries to find
periods where all resources are available to work together.
As late as possible: Task is planned from end to start.
Validated end date must be set-up
Regular between dates: Planning will be equally dispatched from start to end. This mode is best
fitted for management activity of recurrent activities not easy to precisely plan.
Validated start date and Validated end date must be set-up
Regular in full days: Same as above but planning will try to fill full days activity and not partial
activity every day.
Regular in half days: Same as above but planning will try to fill half days activity.
Fixed duration: Similar to regular, but with no validated dates. The activity is floating depending
on predecessors. The duration of this activity will always be kept, even if no work is assigned or left.
A milestone also has a planning mode, possible Planning modes are :
Floating: milestone will move depending on dependencies
Fixed: milestone will never move from fixed date
Planning (5/5)
Planning is bases on Progress elements :
start date,
end date,
duration,
work,
declined on several level:
requested,
validated,
assigned (only for work),
planned,
real,
left (only for work).
Requested and Validated are read/write, as committed elements.
Assigned work is directly calculated through assignment to activity (sum of work).
Planned data is calculated through planning functionality (and is read only).
Real data is calculated through imputation data (real work) and real end date also
depends on status of the activity.
Left work is directly what the user input in imputation form.
So, in Progress section (of Activity or Project) columns planned, real and left
are read only.
Projects portfolio
Planning can be displayed on a projects portfolio point of view.
Resource Planning
Planning can be displayed on a resource basis.
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
All others behaviors are similar to the task planning screen.
Diary Planning
Planning can be displayed on a calendar view. This view can be monthly, weekly or daily.
Just click on any item to directly access the description of the item.
Use top buttons to change current month (or week or day)
Click on week number button to go to Week
display mode
Report
Select the Category of report in the List.
This will update the report list
Update the
Click on
Click on
Click on
Clich on
Requirement (1/3)
Requirements are rules that must be applied to a product.
In most IT projects, requirements are functional rules for a software.
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
requirement
Locked
Locked by
Locked since
Fields
Requirement (2/3)
Field
Description
Id
Project
Product
Requirement
type
Type of requirement.
Name
Field
Description
Top requirement
Status
Responsible
Criticality
Feasibility
External
reference
Technical risk
Creation
date/time
Estimated effort
Requestor
Urgency
Handled
Description
Done
Can be changed.
Field
Description
Linked elements
Attachments
Notes
Change History
Cancelled
Target version
Result
Dependencies
Requirement (3/3)
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.
Planned, Passed, Blocked, Failed : number of test cases on a test session in the corresponding status.
Issues : number of tickets linked to the requirement
Fields
Field
Description
Field
Description
Id
Project
Parent test
case
Status
Responsible
Priority
Handled
Done
Product
Product
version
Test type
Name
External
reference
External reference for the test case (for instance the reference
in a external test case tool)
Closed
Creation
date/time
Cancelled
Environment
Prerequisite
Can be changed.
Contexts are initialized for IT Projects as Environment, OS
and Browser.
This can be easily changed in the Contexts definition screen
Description
If left blank and test case has a parent, parent prerequisite will
automatically be copied here.
Expected
result
Summary
Dependencies
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
Attachments
Notes
Change History
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
Fields
Field
Description
Parent activity
Project
Parent session
Status
Product
Responsible
Product
version
Handled
Flag to indicate that session has been taken into account (first
analysis is done). Date of handling is saved.
Session type
Done
Name
External
reference
Creation
date/time
Description
Field
Description
Id
Can be changed.
Field
Description
Linked elements
Attachments
Notes
Change History
Cancelled
Result
Field
Description
Assignment
Dependencies
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
Quotation (1/2)
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
Project
Field
Description
Type
Type of quotation.
Status
Name
Responsible
Issuer
Send date
Origin
Offer validity
Customer
Handled
Contact
Done
Description
Closed
Additional
info
Planned work
PPD
Price Per Day for the quotation. It represent the cost of one
work day.
Planned amount
Planned end
date
Activity type
Comments
Field
Description
Attachments
Notes
Change
History
Order (1/2)
An order (also called command) is the trigger to start work.
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
Field
Description
Status
Id
Responsible
Project
Handled
Type
Type of order.
Done
Name
Closed
Customer
Contact
Work
External
reference
PPD
Price Per Day for the order. It represent the cost of one work
day.
Submitted
date
Amount
Activity type
Issuer
Origin
Comment
Description
Start date
End date
Additional
info
Field
Description
Attachments
Notes
Change History
Fields
Field
Description
Field
Description
Id
Status
Project
Resource
Type
Type of expense.
Name
Description
Planned
amount
Real date
Real amount
Closed
Field
Description
Attachments
Notes
Change
History
Detail
Field
Description
Name
Date
Type
Amount
Fields
Field
Description
Field
Description
Id
Status
Project
Type
Type of expense.
Name
Description
Planned
amount
Real date
Real amount
Closed
Field
Description
Attachments
Notes
Change
History
Term (1/2)
A term is a planned trigger for billing.
Terms are mandatory to bill Fixed price project.
You can define as many terms as you wish, to define the billing calendar.
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
#id
Id of the trigger
Name
Status
Click
on the corresponding section to add a
trigger (activity, milestone or project)
Predecessor pop up will be displayed.
Click on
Click on
Fields
Term (2/2)
Field
Description
Field
Description
Id
Real amount
Name
Real date
Project
Bill
Validated
amount
Validated date
Read only.
Closed
Flag to indicate that term is archived. Term will not appear in lists
any more, unless show closed is checked.
Read only.
Read only.
Planned
amount
Planned date
Read only.
Read only.
Field
Description
Notes
Change
History
Bill (1/3)
A bill is a request for payment for delivered work.
Billing will depend on billing type defined for the bill.
Each bill is linked to project, a project has a project type, and a project type is linked to a billing type.
So billing type is automatically defined from selected project (field is read only).
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.
Not billed : no billing is possible for these kinds of projects.
Used for instance for : internal projects, administrative projects
Each bill has bill lines.
Input for each bill line depends on billing type.
Fields
Bill (2/3)
Field
Description
Field
Description
Id
Bill id
Bill type
Name
Status
Date
Project
Customer
Customer who will pay for the bill. Automatically updated from
project customer.
Bill contact
Recipient
Billing type
Field
Description
Notes
Change
History
Closed
Untaxed
amount
Tax
Tax rate
Full amount
Comments
Lines
Bill (3/3)
Manual billing
Field
Description
Quantity
Description
Detail
Price
Sum
Term
Resource
Activity price
Start date
End date
Some
Some
Some
Some
fields
fields
fields
fields
are
are
are
are
not displayed
not displayed
read only out
read only out
on creation.
on update.
of creation.
of update.
Activity Price
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
Project
Activity type
Name
Price of the
activity
Daily price of the activities of the given activity type and the
given project
Sort order
Closed
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.
The risk management plan is a key point to Project Management :
- identify risks and estimate their severity and likelihood.
- identify mitigating actions
- identify opportunities
- follow-up actions
- identify risks that finally occur (becoming an issue)
Fields
Risk (2/2)
Field
Description
Status
Field
Description
Id
Project
Responsible
Type
Type of risk.
Priority
Name
Creation date
Issuer
Planned end
date
Handled
Origin
Cause
Impact
Done
Severity
Closed
Likelihood
Result
Criticality
Description
Field
Linked elements
Attachments
Notes
Change History
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.
The risk management plan is a key point to Project Management :
- identify risks and estimate their severity and likelihood.
- identify mitigating actions
- identify opportunities
- follow-up actions
- identify risks that finally occur (becoming an issue)
Fields
Opportunity (2/2)
Field
Description
Status
Field
Description
Id
Project
Type
Type of opportunity.
Name
Creation date
Issuer
Origin
Opportunity
source
Impact
Severity
Priority
Handled
Done
Closed
Result
Expected
improvement
Field
Description
Criticality
Linked elements
Description
Attachments
Notes
Change History
Issue (1/2)
An issue is a problem that occurs during the project.
If the Risk Management Plan has been correctly managed, issues should always be occurring identified Risks.
Actions must be defined to solve the issue.
Fields
Issue (2/2)
Field
Description
Status
Field
Description
Id
Project
Type
Type of issue.
Name
Creation date
Issuer
Cause
Impact
Criticality
Priority
Description
Planned end
date
Handled
Done
Closed
Result
Field
Description
Linked elements
Attachments
Notes
Change History
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.
It is also a good way to organize the meetings.
Define the list of attendees, as you could do in a email receivers list : enter resources or contacts names,
separated with commas or semicolons. You can enter resource names, user names or initials, without caring
about the case :
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.
Then, you can send an invitation to the attendees :
They will receive the invitation in their calendar management tool (Outlook, Gmail, ).
Fields
Meeting (2/2)
Field
Description
Parent activity
Status
Field
Description
Id
Project
Meeting type
Type of meeting.
Responsible
Meeting date
Handled
Name
Location
Done
Assignment
Minutes
Description
Field
Description
Linked elements
Attachments
Notes
Change History
Fields
Field
Description
Id
Project
Meeting type
Name
Location
Assignment
Other
attendees
Description
Field
Description
Parent activity
Responsible
Closed
Field
Description
Period
Time
Periodicity
Only on open
days
Field
Description
Linked elements
Attachments
Notes
Change History
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.
Fields
Decision (2/2)
Field
Description
Status
Field
Description
Id
Project
Decision type
Type of decision.
Name
Description
Decision date
Origin
Accountable
Closed
Field
Description
Linked elements
Attachments
Notes
Change History
Question (1/2)
Question are stored to keep trace of important Questions and Answers.
In fact, you should keep trace of every question and answer that have an impact to the project.
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.
Fields
Question (2/2)
Field
Description
Id
Project
Question type
Type of question.
Name
Creation date
Field
Description
Status
Can be changed.
Responsible
Issuer
Description
Planned due
date
Replier
Handled
Done
Field
Description
Linked elements
Attachments
Notes
Change History
Closed
Response
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.
The information in the screen is read-only.
Alerts
You can have a look at the alerts sent.
By default, administrators can see all the alerts sent, and other users only see their own alerts.
This screen is read only.
If you are the receiver of the alert, and the alert is not tagged read yet (for instance you clicked remind me
when alert was displayed), you will have a button to mark as read the alert.
Message
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.
The message will be displayed in a color depending on the Message type
Field
Description
Id
Title
Message type
Type of message.
Profile
Project
User
Closed
Field
Description
Message
Import (1/2)
Imports work from CSV or XLSX files.
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.
Dates are expected in format YYYY-MM-DD.
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)
Select the element type from the list. The
content of the imported file must fit the element
type description.
To know the data that may be imported, click on
the
button.
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.
Automatic Import
Imports can be automated : files placed on a defined directory will automatically be imported.
The files must respect some basic rules :
File name is : Class_Timestamp.ext
The files are in the standard ProjeQtOr format for import (CSV or XLSX)
Files must be full and consistent : if the creation task may take some time, the files
should not be directly created in the target folder; they must be created in a
temporary folder and moved afterwards.
You just have to define the Cron parameters in the Global Parameters screen.
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
Resource
Or Contact
Or User
Rate (%)
Closed
Flag to indicate that user is archived. User will not appear in lists
any more, unless show closed is checked.
Description
Field
Description
Change History
User (1/2)
The User is a person that will be able to connect to the application.
The login id will be the user name.
To be able to connect, user must have a password and a profile defined.
The issuer of items is a user.
Field
Description
Id
User name
Email address
Password
Profile
Locked
Photo
Is a contact
Is a resource
Initials
Initials of user
Name
Resource and/or Contact name. Can contain first and last name
Mandatory if Is resource or Is contact is checked.
Locked
Field
Description
Change History
Closed
Flag to indicate that user is archived. User will not appear in lists
any more, unless show closed is checked.
Description
Affectations
User (2/2)
Click on
Field
Description
Id
Id of the affectation
Project
Resource
Rate
Closed
Description
Resource (1/2)
Field
Description
Id
Name
Photo
Initials
Capacity
(FTE)
Is a contact
Is a user
User name
Field
Description
Change History
Profile
Team
Calendar
Email address
Phone
Mobile
Fax
Closed
Description
Resource (2/2)
Field
Description
Function
Cost
Start date
Start date for the cost of the resource, for the selected function.
Not selectable for the first cost of a given function for the
resource.
Mandatory for others. Then previous cost will be updated to
finish at date minus 1 day.
Click on
Field
Description
Id
Id of the affectation
Project
Resource
Rate
Closed
Contact (1/2)
The Contact is a person into the organization of the customer.
The requestor of a ticket must be a contact.
It can be interesting to define all the informative data of the contact to be able to contact him when needed.
Field
Description
Id
Name
Customer
Photo
Is a resource
Initials
Is a user
Profile
User name
Email address
Field
Description
Phone
Address
Mobile
Fax
Closed
Description
Field
Description
Change History
Affectations
Contact (2/2)
Field
Description
Id
Id of the affectation
Project
Resource
Rate
Closed
Customer
The Customer is the entity for which the Project is set.
It is generally the owner of the project, and in many cases it is the payer.
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
Customer
name
Customer
code
Delay for
payment
Delay for payment (in days) that can be displayed in the bill.
Tax (%)
Tax rates that are applied to bill amounts for this customer.
Closed
Description
Field
Description
Change History
Field
Description
Address
Projects
Contacts
Recipient
The Recipient is the beneficiary of bill payments.
Recipients are mainly defined to store billing information.
Field
Description
Field
Description
Id
Designation
Name
Street
Company
number
Complement
Complement of address
Tax number
Zip code
Zip code
Tax free
State
State
Closed
Country
Country
Bank
Bank name.
Country
Key
Account
number
Description
Change History
Team
Team is a group of resources gathered on any criteria.
A resource can belong to only one team.
The actual version of the tool does not use much of team notion.
Field
Description
Field
Description
Id
Name
Team
members
Closed
Description
Field
Description
Change History
Field
Description
Project
Resource
Rate
Closed
Product
Product is the element de project is built for.
A project works on one or more versions of the product .
A product is any element delivered by the project. For IT/IS Projects, products are generally Applications.
Field
Description
Field
Description
Id
Products
versions
Name
Customer
Prime
contractor
Creation date
Closed
Description
Description
Attachments
Notes
Change History
Version
Version is the declination of the product life.
A project works on one or more versions of the product .
A version of product is any stable status of the element delivered by the project. For IT/IS Projects, versions
are generally Applications Versions.
Field
Description
Id
Product
Name
Prime
contractor
Responsible
Creation date
Entry into
service
Initial, planned and real entry into service date of the version.
Done is checked when real is set.
End date
Description
Field
Description
Project
Version
Start date
End date
Closed
Flag to indicate that link is not active any more, without deleting it.
Field
Description
Attachments
Notes
Change History
Context
The contexts defines list of elements selectable to define ticket 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
Context type
Name
Sort order
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
Calendar (1/2)
Planning dispatches work on every open days.
By default, open days are days from Monday to Friday, excluding week ends.
The Calendar screen sets possibility to defined off days (for instance New Year, National day).
As these days are different from one country to the other, is must be entered manually.
On the calendar screen, you can also define some specific opened week-end days.
The calendar information is taken into account when calculating planning.
You must re-calculate an existing planning to take into account changes on the calendar.
Up to V4.0, only one calendar is managed in the tool.
Each item only defines exception to standard open / closed days.
You cannot defined several calendar, for instance to get one calendar per resource.
Since V4.1, it is possible to define several calendars.
Then, each resource must be linked to a calendar.
Planning calculation takes into account availability of each resource depending on his calendar.
On global planning display (Gantt, Real work allocation), off days are displayed from Default calendar, which has id
1. For this reason, this calendar cannot be deleted.
Calendar (2/2)
Field
Description
Field
Description
Id
Year
Name
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
The document directories define a structure for document storage.
The document files (defined on document version) will be stored in the folder defined as location in the
document root place. Document root is defined in the global parameters file.
the defined structure.
Field
Description
Id
Parent
directory
Name
Location
Product
Default type
Closed
Function
The function defines the generic competency of a resource.
Field
Description
Id
Name
Sort order
Closed
Description
Status
The status is a important element of items lifecycle.
It defines the progress of the treatment of the element.
Some automations are implemented, depending on status definition, to set handled, done and closed flags
on items.
Field
Description
Id
Name
Handled
status
Done status
Closed status
Color
Sort order
Closed
Quality level
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.
Description
Id
Name
Color
Icon
Sort order
Closed
Flag to indicate that quality level is archived. Quality level will not
appear in lists any more, unless show closed is checked.
Health Status
The health status is a manual indicator for the health of a project.
It defines in a visual way the global health of the project.
It is displayed on Today screen, for each project, as a Red / Amber / Green traffic light.
Description
Id
Name
Color
Icon
Sort order
Closed
Overall progress
The overall progress is a manual indicator for global progress of a project.
It defines in a visual way the global progress of the project, independently from work progress.
It is displayed on Today screen, for each project.
Field
Description
Id
Name
Sort order
Closed
Trend
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.
Description
Id
Name
Color
Icon
Sort order
Closed
Likelihood
The likelihood is the probability for a risk to occur.
The more likely a risk is, the more critical it is.
Field
Description
Id
Name
Value
Color
Sort order
Closed
Criticality
The criticality is the importance of an element to its context.
The risk criticality designs the level of impact the risk may have to the project.
The ticket criticality is the estimated impact that the subject of the ticket may have to the product.
Field
Description
Id
Name
Value
Color
Sort order
Closed
Severity
The risk severity designs the level of impact the risk may have to the product.
Field
Description
Id
Name
Value
Color
Sort order
Closed
Urgency
The ticket urgency is an element given by the requestor to indicate the quickness of treatment needed for
the ticket.
Field
Description
Id
Name
Value
Color
Sort order
Closed
Priority
The ticket priority defines the order to treat different tickets.
Field
Description
Id
Name
Value
Color
Sort order
Closed
Risk level
The risk level measures the technical risk of implementation of a requirement.
Field
Description
Id
Name
Color
Sort order
Closed
Flag to indicate that risk level is archived. Risk level will not
appear in lists any more, unless show closed is checked.
Feasibility
The feasibility defines the first analysis of implementation of a requirement.
Field
Description
Id
Name
Color
Sort order
Closed
Efficiency
The efficiency measures the result of an action.
Field
Description
Id
Name
Color
Sort order
Closed
Predefined note
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
Id
Element
Type
Name
Text
Closed
Description
Workflow (1/2)
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
Id
Name
Sort order
Closed
Descriptio
n
Table
Workflow (2/2)
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
Id
Field
Description
Element
updated
Mail
addressees
New status
New status. Positioning the element sto this status will generate
emails.
Or other
event
Closed
Flag to indicate that Status Mail is archived. Team will not appear
in lists any more, unless show closed is checked.
Reply to emails
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.
Field
Description
Id
Ticket type
Urgency
Value
Value of delay.
Unit for the value can be :
- days :
- hours :
- open days :
calculation excluding off days (week-ends and
off days defined on calendar)
- open hours : calculation only on the standard open hours
defined on the global parameters.
Closed
Indicator
It is possible to define indicators on each type of element.
Depending on type of elements the type of indicators that can be selected in list differs.
Some indicators are based on delay (due date), some on work, some on cost.
For each indicator a warning value and an alert value can be defined.
Field
Description
Id
Element
Type
Urgency
Reminder
Alert
Closed
Field
Description
Mail
addressees
Internal alert
receivers
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
It is possible to define checklists on each type of element.
When a checklist definition exists for a given element, a new button
Field
Description
Id
Element
Type
Closed
Field
Description
Name
Sort order
Choice #n
Exclusive
Project type
Project type is a way to define common behavior on group of projects.
Some important behavior will depend on code :
OPE :
Operational project.
Most common project to follow activity.
ADM :
Administrative project
Type of project to follow non productive work : holidays, sickness, training,
Every resource will be able to enter some real work on such projects, without having
to be affected to the project, nor assigned to project activities.
Assignments to all project task will be automatically created for users to enter real
work.
TMP :
Template project.
These projects will not be used to follow some work.
They are just designed to define templates, to be copied as operational projects.
Any project leader can copy such projects, without having to be affected to them.
Field
Description
Id
Name
Code
Workflow
Defined the workflow ruling status change for items of this type
Sort order
Billing type
Closed
Description
Ticket type
Ticket type is a way to define common behavior on group of tickets.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Activity type is a way to define common behavior on group of activities.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Milestone type is a way to define common behavior on group of milestones.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Sort order
Result
Closed
Lock handled
Description
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
Lock canceled
Order type
Order type is a way to define the way the activity references by the order will be billed.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Sort order
Result
Closed
Lock handled
Description
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
Lock canceled
Field
Description
Field
Description
Id
Description
Name
Workflow
Defined the workflow ruling status change for items of this type
Lock closed
Defines whether the done check is locked or not for items of this
type.
Sort order
Closed
Description
Field
Description
Field
Description
Id
Description
Name
Workflow
Defined the workflow ruling status change for items of this type
Lock closed
Defines whether the done check is locked or not for items of this
type.
Sort order
Closed
Description
Field
Description
Id
Name
Sort order
Value / unit
Closed
Description
Bill type
Bill type is a way to define common behavior on group of bills.
Field
Description
Field
Description
Id
Description
Name
Code
Lock done
Defines whether the done check is locked or not for items of this
type.
Workflow
Defined the workflow ruling status change for items of this type
Sort order
Closed
Description
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.
Risk type
Risk type is a way to define common behavior on group of risks.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Opportunity type is a way to define common behavior on group of opportunities.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Action type is a way to define common behavior on group of actions.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Issue type is a way to define common behavior on group of issues.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Meeting type is a way to define common behavior on group of meetings.
Meeting type is also used for periodic meetings definition.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Decision type is a way to define common behavior on group of decisions.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Ticket type is a way to define common behavior on group of tickets.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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).
Field
Description
Field
Description
Id
Description
Name
Color
Sort order
Closed
Description
Document type
Document type is a way to define common behavior on group documents.
Field
Description
Field
Description
Id
Description
Name
Code
Workflow
Defined the workflow ruling status change for items of this type
Sort order
Closed
Description
Context type
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
Name
Closed
Description
Requirement type
Requirement type is a way to define common behavior on group of requirements.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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.
Field
Description
Field
Description
Id
Description
Name
Code
Responsible
Workflow
Defined the workflow ruling status change for items of this type
Result
Sort order
Lock handled
Closed
Description
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
Customer type is a way to define different status of customers (prospects or clients)
Field
Description
Field
Description
Id
Description
Name
Sort order
Closed
Description
Profile
The profile is a group of habilitations and right access to the data.
Each user is linked to a profile to defined the data he can see and possibly manage.
Field
Description
Id
Name
Profile code
Sort order
Closed
Description
Access mode
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 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
Id
Name
Read rights
Create rights
Update rights
Delete rights
Sort order
Closed
Description
Access to forms
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.
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)
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
Administration screen access should be restricted to administrators.
Background task is a specific threaded treatment
that regularly checks for indicators to generate
corresponding alerts and warnings when needed.
Audit connections
Audit connection proposes a view of who is online.
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.
Specific parameters about Gantt planning presentation.
Select if resource can be displayed in Gantt chart, and format for
display : name or initials.
Select max project to display (to avoid performance issue).
Propose possibility to display old style Gantt : may cause
performance issue but could fix some display issue on browsers.
Behavior of real work allocation screen, to define displayed
tasks, and set handled status on first real work.
For instance, with this formatting definition, first version of the ARD should have
reference = MyProj-Technical-0123-Architecture Dossier-V1.0.doc
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
Standard Ports :
localhost
25
ssl://smtp.gmail.com
465
yourname@gmail.com
*********
25
tls, without authentication
587 tls, with authentication
465 ssl, with authentication
using php mail function : this function allows only anonymous connection
using PHPMailer library : this advanced method allows anonymous and authenticated connections
You can select the method just adding $paramMailerType in your parameters.php file :
smtp.free.fr
25
(2) Some fields have no sense for some items, and most have
none for Mails to User.
User parameters
User parameter screen access should be allowed to all users.
User parameters are efficient even without saving.
Saving parameters will retrieve the selected parameters on each connection.
Translatable name
Some items have a translatable name.
This means that when you have such an item, what is displayed is not directly its name, but a translation of its
name.
These items are easily identified : they have a property $_isNameTranslatable = true;
Most of these items are internal lists, not updatable through the tool.
But two of them can be modified : "profile" and "access mode".
They are easily identified, because under the name field appears the translated name (display only).
This means you can add one new item, but then how do you set its name ?
Here is an example on how to add a new profile :
Add the new profile, and set its name to a significant value, without spaces or special characters, and idealy
starting with "profile" (to be easily identified in the translation table). For instance, we will name it
"profileNewValue".
Enter all the other values as desired and save.
After saving, you can see displayed value is "[profileNewValue]", meaning this value is not found in the
translation table.
You must then add a new line in the lang.xls file. First download it from the "download" menu.
Open in in Excel, and allow macros.
Then, you must add a new line in lang.xls, with string="profileNewValue" (example) and default, en, fr and de
columns with the caption you want to display.
Then, "save as" (to position the default directory in Excel, don't use direct "save") and click on "Generate".
This will generate a lang.js file in the current directory and in the en, fr and de sub-directories.
Then you may copy these files to replace existing ones in the /tool/i18n/nls directory on your server.
Just display the profile again : the name is now translated.
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
Basically, you should at least see the emails you've sent.
But you can also have visibility on all your project's emails or all the emails.
This can be done by the administrator, who can parameter sent emails visibility.
Sure he will reserve to himself the last option (see all the emails).
API
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.
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.
Json format retrieved from GET can be used for PUT, POST and DELETE.
API
Method
Url
Result
GET
GET
http://myserver/api/{object class}/all
Ex : http://myserver/api/Project/all
GET
GET
POST
http://myserver/api/{object class}
data provided in json format as POST value
PUT
http://myserver/api/{object class}
data provided in json format as a file
DELETE
http://myserver/api/{object class}
data provided in json format as a file
API
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
Field
Description
Type
Id
Name
Status
Date
User
Attachments
icon.
Field
Description
Id
Size
Type
File
File name.
Date
User
Attached files are stored on server side, on a place specified by the administrator on parameters.
Attachment 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).
Files can be directly attached using drag & drop move into the devoted zone.
Notes
Field
Description
Id
Date
icon.
Type
Note
Change History
Field
Description
Date
User
Operation
Data
Value before
Value after
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
Backup is a good practice.
You should regularly backup your Data to be able to retrieve it is case of a crash.
How often ?
It just depends on your need ...
Just ask yourself : what is acceptable to loose in case of a crash ? 1 day, 1 week ?
You should also always backup your Data before any application upgrade... in case of ...
So, how to back-up ?
The simplest way is to use phpMyAdmin or phpPgAdmin (depending on Database format) export capacity, using
"SQL" format, saving result to a file.
Another great tool is MySqlDumper.
Then you'll be able to import Data from this exported file.
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...)
Attachments and documents are not stored in database.
They might be backed up separately if needed.
Shortcuts
Shortcut keys
Effect
[CTRL]+s
[F1]
[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."
This simply means that whatever your planning is, it is wrong !
So, youd better manage risks and follow-up all the events on your project
Based on ProjeQtOr :
4.3.0