Kanban: control in JS preventing save with alert message "mandatory fields. Ticket-Mail with attachment leads to brocken ticket Ticket: no scroll bar on "dispatch work dialog " if many entries Timesheet validation : control over FTE of resource must not be roundedĪssignment of whole team to meeting : incorrect convertion if work defined in hoursĬopy a workflow under postgres does not work
#JOOMLA 2.5 BUTTONBAR FULL#
Replace phpExcel with phpSpreadsheet in HR moduleĬonsistency Check : add check on assignement for Periodic MeetingĬlosing Test session with many test case runs is long : search for performance improvmentĬheck isContact on user : full name should be required Use some caching for Plugin, PluginTriggerElement, ParameterĬreate new function SqlElement::getTypeName() and SqlElement::getPlanningElementName() Specific access right for validation of real work : should be applied on Validation screen
Gantt CSV Export : export all lines, not only "visible lines"Īdd new criteria "Assignment function" or reports "work detail per resource" (for 4 periods) Reports : Save position of horizontal slider when manually changedĪccess to reports by the left menu to be improved in the case of a sub-menu Ticket on status Paused - Message when trying to start workĬonsistency check : add consistency check on BBS structure and "is budget item" flagĪlerts on input real work by others : have possibility to select "none" Give possibility to preserve copy options for specific target copyįor some screen resolutions, options on Real Work validation not visible Sort Assignment table (on Activity and else) by Name of resource If a favorite list of projects is selected, retreive it after disconnection / reconnection When left menu is "closed" enlarge list rather that detail (keep detail size) Todo lists : homogeneize status and caption of switchĪllocation screen : add alert when deleting self allocationĬopy option : move directly to status "recorded" Today : Replace "Documents to approve" with "Items to approve" Give possibility to qualify recuring "absences"Ĭopy Risks / Opportunity when copy project When filter on type is applied (with hide option) activities should not be displayed on Gantt chart Improvement management of replacement of ressource "between dates"įorbit to change status to done if todo lists items are not all set to "done" On timesheet add quick filters on id and name, like object listĪctivity stream: when filter by author give possibility to show answer of notes Several performance improvments to speed up response time Restrict reading of simple object, without its dependant objects when the whole structure of the object is not required : done for Projects and Acitivities Use of caching of object, when possible, to avoid duplicate access to the database for same data
ĭefault collation is now utf8mb4_general_ci Will allow extended storage in Database : emoticons, special chinese characters. Management of voting target for each item (number of points needed) Management of voting on items, in the limite of points for users or clients (a contact may use points of clients) Management of rules for voting on items (max points, blocking stauts) Management of rules to give points to users (fixes value, or new points per week / month / year) or clients Possibility to manage attribution of points on Tickets / Activities / Requirements On assignment, possibility to search best resource from skills required for the activity Search for resources with a defined skill, with availability of the resource and relevance rateĭefinition of skills required for an activity, with required level V10.0.0 Major evolutionsĭefinition of list of skills, with hierarchic definitionĭefinition of resource skills, selecting skills and level (and also dates for use of the skill) for the resource IF YOUR INSTANCE WAS FIRST INSTALLED BEFORE V4.4 OF PROJEQTOR, YOU MAY NEED TO CONVERT YOUR DATABASE TO RETREIVE CORRECT DISPLAY FOR ACCENTUATED CHARACTERS. ** TO BE SURE NOT TO LOOSE ANY DATA, YOU MUST BACKUP YOU DATABASE BEFORE MIGRATION ** THIS VERSION INCLUDES A MAJOR CHANGE IN DATABASE MANAGEMENT (use of UTF8MB4)
0 kommentar(er)
