• Home
  • Project
  • Screenshots
    •  


    Features

    The list bellow contains the main features already implemented on Plandora until version 0.9.1:

  • Multiples roles into system. Project Leader, Project Resource, Customer and System Administrator (Root). Each role is associated with different features into system.
  • The system supports multiples projects, where each project has one or more leaders, one or more resources and one or more customers. (see the screenshot)
  • The system provides customer GUI to open Requirements and follow the status of opened Requirements. (see the screenshot)
  • The Leader of project is able to check and approve/refuse the requirements coming from customers. The project resources won't be involved until the request is approved. (see the screenshot)
  • The Leader is able to link one or more tasks with a request and to assign it to a specific project resource.
  • The tasks of resources can be updated and visualized by project leader in any time through a Gantt chart. (see the screenshot)
  • The task working time from the resource TO DO list, can be updated and will be considered dynamically by the Gantt chart and eventually will change the status of request viewed by customer requester. (see the screenshot)
  • The system administrator is able to configure for each project, key indicators (KPI) which follow the concept of BSC (Balanced Scorecard). Each KPI is actually a SQL statement, and for this reason, can be easily customized for any situations. (see the screenshot)
  • The system administrator is able to create requirement categories for a specific project. It is useful to categorize types of requests (for example: if the project is in compliance with the ITIL Service Desk the categories can be set to Incidents, Problems, Changes, etc)
  • The tool implements the concept of Meta Fields. A Meta Field is a visual element (text box, combo box or a SQL combo box) created by system administrator and can be related with the requirements of a specific project. The Meta Fields is useful to give more customization for the requirements input. (see the screenshot)
  • The Plandora tool is multiplatform. It is written in Java and runs in any operational system that supports the Java language.
  • Plandora was designed and tested under a free data base (MySQL) and free web server (Jakarta Tomcat).
  • The Plandora tool is royalty free for any purposes. Anyone is allowed to use, modify and resell fully or partially this system (including commercial usage). For more information, check the GPL terms of use.

    • Coming Soon...

    The list bellow (without priority order) contains the features that are part of road map and might be implemented soon:

  • Extension of Meta Fields feature to task entity;
  • Discussion Forum by project;
  • Import data from MS-Project, Gantt Project (sourceForge) and Google Calendar;
  • Export data to MS-Project and Google Calendar;
  • Attachment files related on a requirements, tasks or projects;
  • Field to link requirements hierarchically;
  • Turn the business rules of system customizable (the state machine of tasks and requirements);
  • Create a list of risks linked with requirements, tasks or projects;
  • Create an API or http call, with some defined rules, to be used by triggers of repositories (for example CVS or Subversion) in order to request to Plandora permission to commit or remove the configuration itens.
  • Create knowledge-base "google-like" indexing information about tasks, requirements, project documents, risks, lesson learned, etc (since version 1.1.0)
  • Customized Reports (use of JasperReports with custom queries); (since version 1.0.0)
  • Customized Alerts. The rules of alerts will be created trough the SQL query and the architecture will allow to build new alert channels (eMail, http post, etc) easily; (since version 1.0.0)

    • Release Notes

    Plandora v0.9.1

    bug fix

  • Requirement form validation method. Problem with null pointer after 'self-requeriment' without a suggested date.
  • Forms of 'All requeriments' and 'All Tasks' displaying resources/customers wronglly
  • If allocation form, the resource combo was displaying the user of current project and (wronglly) the child projects.
  • Some messages/labels of table taglib weren't in i18N.
  • After task closing they still had been displayed into main form (even the task had been closed more than 1 week).

    • features

  • Creation of priority option 'to be defined' for requirements
  • Now the leader is able to disable a leader/resource/customer to participate specific project.
  • Implementation of support for english language en-US and spanish es-EN
  • Colored bullets into grids of task screen in order to show the current status of task
  • The field username was enlarge to 30 characters
  • Implementation of preferences to set the number of cells words of name/descriptions of grids (default value = 20)
  • Now the task status combo is dinamically, according with the task state machine. Now the combo display only the allowed status.
  • The grids of main form and requirement form are ordered now
  • Into the main form was implemented anchors to improve the navegability
  • Implementation of 'changing password' feature into preferences screen.
  • The password is stored into data base with criptografy in order to keep the user privacy.
  • Implementation into Gantt of 'redim bar' of left lateral box
  • Implementation of SAVE button into Gantt and the infra-structure to update the tasks upon the Gantt (only for moving/redim of Jobs and edition of task capacity)
  • Implementation of feature of configuring the max capacity for each resource for each project (default=480min)
  • Configuring the max records to be displayed by "My Requirements" and "My Tasks" grids. (configurable by preferences screen)
  • For requeriment list into main form, the requiments with reject/canceled and closed are displayed with red or green color.
  • Visual improving for history popups (requirements and task). Keep the same size independentlly of lines number and to allow the copy of history comments (before the content used to be displayed into msgbox...)
  • Implementation of feature to allow/to forbid (default) a customer of specific project to see the technical comments of project resource.
  • Creation of Category form to be managed by user root (a category can be setted to specific project and be used for task or requirements)
  • A category field was inclued into requirment form
  • Implementation of Meta Fields feature. The meta fields can be populated by root used and linked with a 'project' and 'one or any category'. When the customer open the requirement form, this 'field' is dinamically displayed into form like a native field. Is possible to create a metafield like a textBox, ComboBox (with static data) and SQLComboBox (with data comming from a SQL pre-defined)
  • For preferences screen of leader is possible to show/hide the fields of "All Requirements" form. This was implemented due to the great number of fields related on requirements (included Meta Fields). Now each leader can customize which fields he needs to view.

    • Plandora v1.0.0

    bug fix

  • [BUG:1553404] - There was a bug after changing a gantt chart by shifting the openning task. It only can succeed to save in server computer but cannot function in any client side computers.
  • [BUG:1288854] - The task screen hasn't been showing correctly the 'task list' when the user select a task without a requirement related.
  • [BUG:1288854] - The task screen hasn't been updating a task without a requirement related.
  • [BUG:1695187] - It was setted to 'task history form' and 'requirement history form' the lateral scrollbar.
  • The system were not requesting appropriately a task comment popup before cancelation action. The bug was fixed.
  • Updating of column 'sql' of table 'report' to 'sql_text' due to a MySQL pre-requeriment for column names.
  • Bug fix into project form, when the user was 'root'

    • features

  • [FR:1208708] Implementation of the report feature
  • [FR:1201490] Implementation of the Notification feature infrastructure (email, http and audit log)
  • [FR:1572493] Implementation the 'pre approve' feature for the requirements. A customer can optionally open a requirement and generate a task (for a project resource) automatically, without leader approving. The 'self-allocation' feature was migrated to this new feature.
  • GanttChart: dash lines separating jobs vertically (between the tasks) in order to improve the visibility and decrease the polution
  • GanttChart: adjustment of dash job mode. The lines was exchanged to small points over the job area.
  • [FR:1638189] Implementation the 'category' filter for "Show All Reqs" form
  • Import/Export: creation of form specific for import/export generation and adjustments of export infra-structure
  • User Form: separation between user management and password management
  • The customer could now re-open a requirement (if allowed). After reopening the requirement back to the "waiting approve" status.
  • [FR:1306438] Visual highlight into main form for delayed tasks. The highlights was painted in according to the number of delayed days (critical and warnig) and is configurable by the user.
  • Change of 'Ongoing Task Form' GUI, in order to input the duration data day by day (not only the working hours)

    • Plandora v1.1.0

    bug fix

  • when a requirement was edit into the Customer Requeriment Form, the information about the project related was not been diplayed correctly.
  • the event_log DB script contain a mistake, causing the misfunction of logging feature. A field 'id' was removed.
  • fix bugs in form of 'on-going task' form

    • features

  • new sub-report into "Project Report" jasper report. Inclusion of Pie graph displaying the resource task duration of project
  • creation of new Report: Comparison between the duration time estimated and actual duration time of project
  • implementation of Project Occurrences form and link with the current project
  • creation of new Report: Occurrence Book
  • implementation of the Knowlegde Base infra structure (using Lucene facilities).
  • categorization facilities for KPIs and Reports
  • the field 'birth' (nullable) was add into User entity.
  • implementation of form to create an 'ad Hoc' task by resource