• Home
  • Project
  • Screenshots
  • Contact
  •  


    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, calendar or a SQL combo box) created by system administrator and can be related with requirements, tasks or risks of a specific project. The Meta Fields is useful to give more customization from the inputs. (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 LGPL terms of use.
  • The information about the projects (task, risks, issues, lesson learned, etc) are automatically indexed and can be searched through a 'google-like' GUI, consolidating a knowledge base of all projects in a colaborative way and with common sharing. (see the screenshot)
  • More...

  • Take a tour of the GUI here and learn basic skills.
  • Try the online demo experience here.
  • Coming Soon...

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

  • Export data to MS-Project and Google Calendar;
  • 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.
  • Make a sequence of tasks follow a customized workflow.
  • Improve Plandora to manage the project costs.
  • Improve Plandora to manage project surveys.
  • Implementation of auto-assignment of tasks based to requirement fields.
  • Extension of Meta Fields feature to project (since version 1.2.0) , risk and task entities (since version 1.5.0) ;
  • Discussion Forum in requirement form (since version 1.2.0) and project;
  • Import data from MS-Project(since version 1.5.0), Gantt Project (sourceForge) and Google Calendar;
  • Attachment files related on a requirements (since version 1.2.0), tasks or projects;
  • Field to link requirements hierarchically; (since version 1.5.0)
  • Create a list of risks (since version 1.2.0) linked with requirements, tasks or projects;
  • 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 wrongly
  • If allocation form, the resource combo was displaying the user of current project and (wrongly) 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
  • Plandora v1.2.0

    bug fix

  • the 'delete occurrence' feature was fixed (was not working at all)
  • some bugs of 'on-going task' form was fixed
  • [BUG:1230952] When a requirement was removed in Main form, the focus was wrongly redirected to the requirement form. This bug was fixed.
  • features

  • implementation of Risk Form and link with the current project
  • Add of RISK type into the category form
  • was included the support of LDAP authentication for each user. The current authentication (Plandora DB) is the default method although
  • the procedure of 'save preferences into DB' was moved from 'logout action' to 'save options action screen'
  • inclusion of Risk entity into Knowledge Base index engine
  • implementation of new GUI Type for Meta Field: TEXT AREA
  • inclusion of meta-field feature into Project Form
  • the table 'user' was renamed to 'tool_user'. The DAO classes related and the DBSscript file was adjusted.
  • was included into project entity a attribute "Allow Allocation?" that define if tasks or requeriments could be set to this project.
  • [FR:1224581] and [BUG:1205906] Implementation of Attachment facilities for requirement form
  • now, it is possible to create and set a Meta Field for all projects.
  • implementation of task removing that can be performed (only) by the owner of task.
  • the report is now configurable by user role. A specific report could be viewed by the leader or resource.
  • implementation of keyword ?#USER_ID# into report SQL field interpretator. This keyword should be used to refer to the id of current user connected.
  • implementation of a grid containing the current allocation time per days into 'on-going task' form
  • now it is possible to adjust the allocation information of a closed/canceled task.
  • now, some information of task (category, name and description) can be updated by user, if this user was the original creator of the task.
  • implementation of discussion forum feature related to the requeriment
  • [FR:1312239] Change the requirement priority in batch by project leader through the "All Requirement" Form
  • [FR:1217731] Now, the project leader is able to allow a customer to view the requirements opened by other customers in the same project (without edition)
  • iplementation of a new Project Occurrence. Now it is possible to create for each project, a number of iterations entry that must be used to control the deliverables and to allow/avoid the priority changing by customer though web GUI.
  • Plandora v1.3.0

    bug fix

  • bug fixed in requirement gantt chart view.
  • the comboBox of macro tasks (Task Allocation form) was wrongly showing macro tasks of different projects.
  • the comboBox of E-mail Notification was losing the selected value.
  • the filter feature of 'My Requirements' and 'My Pending Requiremes' grids in main form wasn't working appropriately.
  • there was a bug in knowledge base searching when the project level was greather than two.
  • when the task was 'in-progress' status the system was not allowing the user to put a zero value in 'actual time'.
  • there was a bug at e-mail notification. When a notification has contained multiples recipients, only the last e-mail address received the message.
  • The save feature of gantt chart was not working appropriately when the login mode was LDAP.
  • features

  • now, the project resources are able to filter through Option Form which projects should be hidden in 'Ongoing Task Form'.
  • in meta fields, the query of SQLCombo field is now able to process keywords like '#PROJECT_ID#' and '#USER_ID#'.
  • was included a button to create a new Ad-hoc task on 'Ongoing Task Form'.
  • now, the default project for Ad-hoc task at 'Ongoing Task Form' is 'None'.
  • now the user can change the apperance of requeriments (the background could be collorized according to the requirement priority).
  • was implemented in 'My Task' grid at main form a collumn that could be used to mark or classify a task (like a pin-point).
  • [FR:1201500] Implementation the Relationship grid at 'Task Form', 'Occurrence Form' and 'Risk Form'. Now, a task, occurrence or risk could be linked with other entities (risks, occurrences, requeriments, tasks, etc).
  • implementation of Meta Form feature. Now it is possible to create customized forms that uses customized fields (meta fields was already implemented since v0.9.1).
  • implementation of Mind Maps that shows graphically the relationship among the entities.
  • The 'iteration' occurrence entry, can be used to classify the requirements in phases, versions, releases, etc.
  • Plandora v1.5.0

    bug fix

  • the grids that has displayed meta_fields was showing data with the same title in different columns.
  • there was unexpected and invalid error message in 'ad-hoc task' form when the user has clicked in 'Next' or 'Previous' button without any project selected.
  • there was enconding errors in GantProject export file. (thanks to NiltonPereira reporting).
  • the 'Occurrence Book' report did not displaying the list of iterations appropriately.
  • the 'risk form' was keeping the list of relationship when the Clear button was pressed.
  • the gantt chart of spanish version was causing an error when the form was opening.
  • there was a but during the cancelation task feature into the task form (when leader canceled a macro-task whose contained a group of tasks).
  • when a task was removed and the user press the refresh button occurs a NullPointerException causing a blank screen. The bug was fixed.
  • was made the performance tunning at 'project form' (for root purposes). The performance of this form was terrible specially with many project records in it.
  • there was an invalid message error at 'task form' when the lider tried to change the assignment of a task.
  • the 'All Requirements Form' eventually appeared with hide columns. This bug was fixed.
  • the sorting feature of "All Requeriment Form" was showing wrongly the meta fields coluns. This bug was fixed.
  • refactoring and bug fix at MindMap popup.
  • a resource was able to view a report without permission.
  • a problem with the wrong position of 'week-end mark' into the 'on-going form' was fixed.
  • The refusing action into "All Requirements Form" was wrongly forwarding to main form.
  • features

  • now, the iteration (occurrence) related with the requirement, appears in 'my tasks' grid.
  • now, the columns of some grids of system could be displayed or hidden according to users preferences.
  • the 'refuse form' (refuse requirement and cancel task) was changed to new look'n feel.
  • the icon to remove a task was included into grid of 'Ongoing Task Form'.
  • now, it is possible to create and set a Meta Field for tasks and Risks.
  • now, reports can be visualized by customers depending on the role set by root at Report Form.
  • was included an occurrence book icon into the project grid at main form.
  • now, it is possible to set a picture (PNG or JPG photo) related to user.
  • now, when the resource set a hide project at option form, the project disapear from 'My Project' grid.
  • now, the resource can set a macro-task related to current task at 'Ad-Hoc' and 'on-going' forms.
  • now, when a risk materalize, the sistem ask if the user want to create a issue (occurrence form) linked with the risk.
  • implementation of gadget feature. A gadget is a chart that can be used to show information about the project.
  • now, the project resources can view a chart at lateral main screen based to a gadget class.
  • now, it is possible to set roles (only for report purposes) for each user allocated into the project.
  • now, the reports of tool could be exported using RTF output format and OpenOffice output format (the same way of PDF format).
  • now, some grids of tool contain a new filter combo (ex.: My Task grid could be filtered by Project, Risks grid and Occurrence grid could be filtered by status).
  • now, the root user could set a category to hidden status. This category will not be displayed at On-going task form.
  • now, the "mindMap Form" displays the relationship qualification between two entities.
  • a new filter (status) was inclued into Requirement Search popup.
  • now, the information about capacity of resource into a specific project could be changed during the all project lifecycle.
  • the rule that blocks a task to be linked with a closed requirement was removed. Now it is possible to link with any requirement from data base.
  • now, the root user is able to view (into the option form) the last actions of user through the tool.
  • now, the system ask confirmation if the resource try to save a task without category selected.
  • the scheduling grid of "on-going form", contain now two navigation buttons to skip by day (besides current weekly skiping).
  • implementation of Repository Project form (SVN navigability integration) - Read Only.
  • now, the requirements could be organized hierarchically. The parent id could be set using the "All Requirements Form".
  • now, it is possible at "All Requirements Form" to display the requirements records using the hierarchy mode or list mode.
  • implementation of Resource Capacity Planning form into project form. Now it is possible to plan the capacity of resource along the project .
  • the look'n feel of knowledge base form was rebuild.
  • the field "Estimated Closure Date" was included into project form.
  • now, the report opens into a popup form.
  • implementation of feature to import the MS-Project v2003 XML file, in order to load new tasks, allocation and dependences.
  • now it is possible to leader, to alloc into the Task Form a "key-resource" called "Anyone". After that, the new task appears to all resource of project waiting the assignment of one of those.
  • Plandora v1.6.0

    bug fix

  • there was a error message into "On-Going Task Form" after clicking the checkBox "Don't display finished tasks after (..)" and "Refresh" button.
  • there was a error when saving a project. The problem occures when a resource was removed from project and a role was set for this resource/project.
  • features

  • implementation of maximization feature of gadgets.
  • Now, the encoding attribute used by export process could be overload by export class (that extends ExportBUS). The default value of encoding is UTF-8.
  • Plandora v1.7.0

    features

  • [FR:2858568] Implementation of Agile Board form.
  • Implementation of export routine of project KPI data to CSV file (filtered by date and KPI category).
  • Performance tunning at main page loading.
  • Before, when the task was cancelled, the tool was reopening the requirement. Now, when the leader try to interrupt the last task related to a requirement the tool ask if the requirement must be reopened or finished.
  • It was created a new column into task list. This column shows what other tasks are blocking the current task.
  • It was included a new column into grid of 'on-going task form'. Now the grid could display the current iteration relatated with the requirement of task.
  • Implementation of Report Button at On-going form. This button shows a PDF report based to the daily tasks of form period set.
  • Now, the leader is able to set (at Project Form) witch project resource must access the Agile Form.
  • Implementation of new fields into risk form (check box of "impact in:" -> "costs", "quality", "escope", etc ).
  • Implementation of 'Execute SQL' notification class. This channel, is able to execute any sql statement into Plandora or another database.
  • Implementation of Gadget chart "Defect Task" to show how many time was spent with bug fix into the project.
  • Implementation of Gadget chart "Predictable Task" to show how many time is related to planned task or unpredictable tasks.
  • Now it is possible to set a dynamic result from SQL column into the email notification Body.
  • The features of login authentication were generalized into specialized authentication classes, following the same pattern of other entities (KB, occurrences, gadgets, import/export, etc).
  • Now, it is possible to project leader to choose files of repository that must be visible by customer view.
  • bug fix

  • There was a bug at KPI Gadget when the interval was 180 days (weekly). The chart has appeared in blank.
  • An 'anyone' task was displayed into 'My Task' panel even after the cancelation of task. The bug was fixed.
  • There was a bug into mind map nodes apperance. Nodes in the same level was displayed wrongly.
  • The password field into data base was increased to 70 caracteres. Noticed that, the content of this field is incrypted, because of this, the field must be more than 15 caracteres.
  • Bug fix at calendar locale. Even user is set to english language, the calendar was showing date using portuguese language.
  • Bug fix at View All Tasks Form. The form was showing a blocked task with 'locked' icon. This icon must be shown only to resources.
  • Adjust of Gadget chart "Billable Task". Some bugs was fixed and the data of chart was changed to task hour format.
  • Bug fix at project combo list of My Task grid. The combo was showing wrongly some projects without relation with current user.
  • The task form (used by leader to create new tasks) was not allowing to create a task with more than 24 hours.
  • In tasks with more than one resource, when one of them set his task to 'closed status', the other tasks were disappearing from other resources 'My Task' list. The bug was fixed.
  • Bug fix at requirements list. In some cases, a requirement - related with a project which the user was not a resource - appears into user GUI.
  • [BUG:2866737] There was a bug when the leader tried to enable a resource that was previously disabled (at project form). The bug was fixed.