AnAS21FilteringEnhancements
TWiki>
LibrePlan Web>AnAS21FilteringEnhancements (01 Feb 2013, LorenzoTilve)EditAttach
| Story summary | Filtering enhancements |
| Iteration | AnA08Usability |
| FEA | AnAS21FilteringEnhancements |
| Story Lead | |
| Next Story | |
| Passed acceptance test | No |
Adding configuration parameters in user preferences for projects planning and projects list perspective
Three new configuration variables will be added in the LibrePlan users:
- Label to use in projects lists. It will save the label that will be use to filter the projects planning and the projects list.
- Ahead planning horizon. Integer number specified in months to specify the projects that from current day want to be included in the filtering result.
- Backwards planning horizin. Integer specified in months to specify the project that want to be included in the results before the current date.
These options will be managed in the user preferences window. By default users will not have any configuration of this filters.
It will be implemented a mechansim to fill the filters in the projects planning and projects lists perspective when a user enters them with the next values:
- Label filter. It will be included the configured label (if any) that the user has selected in his configuration parameters.
- Start date filter. It will be filled with the value: Current date minus backwards planning horizon
- End date filter: It will be filled with the value: Current date plus ahead planning horizon.
With the regard to the label filter, the query will get all the projects that have assigned the label in the root of the project.
User session store of the last value of the filters used in the projects planning and projects list view
It will be implemented a mechanism so that, on filling some value in the filters of the projects planning or the projects list perspective and the filter is exectued, in that moment, they will be saved in the user session those values.
The specific filters that will be soaved are:
- Criteria and labels sequence. Combination with one or more label values and criterion that the projects can have assigned.
- Start and end date.
It will be implemented also a mechanims so that when the user visits the projects planning or the project list screens, if there are some filtering values stored in the user session, a filtering is executed with those parameters.
Three new variables will be added:
- Criterion to be used in resource load. It will track the specific criterion that will be used for filtering in the resource load. It will allow to filter by a single criterion, I mean, it will not be possible to configure several criteria.
- Ahead horizon in resource load. Integer number specified in months to specify the start of the interval to show the resource load in the filtering result.
- Backwards horizon in resource load. Integer specified in months to specify the end of the interval to show the resource load in the filtering result.
These options will be managed in the user preferences window. By default users will not have any configuration of this filters.
It will be implemented a mechanism to fill the filters in the resource load view with the next values:
- Criterion filter. It will be included the criterion configured in the connected user parameters.
- Start date. It will be filled with the value: Current date minus backwards horizon in resource load
- End date. It will be filled with the value: Current date plus ahead horizon in resource load.
With regard to the filter, the query will get all the resources and their bounded load that satisfy the criterion configured during the filtering time interval specified.
It will be implemented a mechanism so that, on filling some value in the filters of the resources load perspective and the filter is exectued, in that moment, they will be saved in the user session those values.
The specific filters that will be soaved are:
- Criteria and resources sequence. Combination of one or more criteria value which the resource have to satisfy and resources names to be included in the load analysis.
- Start and end date.
It will be implemented also a mechanims so that when the user visits the resource load view, if there are some filtering values stored in the user session, a filtering is executed with those parameters.
This task consists of implementing a memorazing mechanism to keep the filtering values in the project planning in the perspectives of projects planning and project details.
The filters values that will be memorized are:
- Task filter. Text string which has to be part of the activity name to be selected.
- Label filter. Label(s) which has to be assigend to the task through the bounded order element (wbs element). If there are several labels, all of them have to be assigned to the task to be selected.
- Criterion. Criterio(s) which are used in any of the resource allocation of the tasks. If there are several criteria all of them have to be assigned in the allocation to satisfy the filtering.
- Date from. Tasks to be selected in the output have to have a start date after the filtering date.
- Date up to. Tasks to be selected in the output have to have an end date before the filtering date.
- Labels without inheritance. It tracks if in the label filtering they are selected in the output tasks which inherits a label or if only the tasks which have the labels directely assigned appeared in the output.
The memorizing mechansim to be implemented will consist of that, on asking for a filtering, the elements that can be memorized are stored in the user session.
The memorized values will be project specific. This means that they will be saved as many filtering different values as projects the user visits during his session.
As part of this task will be implemented too a procedure to fill the filtering and execute it with those value when a user enters a project in the planning perspective or the project details perspective.
Copyright (c) by the contributing authors. All material on this collaboration platform is the property of the contributing authors.