The component that shows the filtering results is adding the unscheduled projects when they
are not excluded by the dates range, but they were appearing also when they were not matching
the combobox conditions.
FEA: ItEr77S15FilteringEnhancements
These icons are disabled when the WBS is showed filtered, as the manipulation
operations could be ambiguous or problematic, but it was treating wrongly
empty predicates.
FEA: ItEr77S15FilteringEnhancements
This will refresh all company-level variables with the corresponding
values depending on the filtering preferences saved.
FEA: ItEr77S15FilteringEnhancements
Either in the Company view/Projects list perspectives and the Project Gantt/WBS ones,
their filter values are synchronized when shitching between them. All the perspectives
were loading the rigth session values when they were loaded for the first time, but
needed to be updated after changes in the filter values to actualize the widgets
on the sibling perspective.
FEA: ItEr77S15FilteringEnhancements
Calling getSelectedElemets was returning a WrongFilterValue exception, and filling
in the bandbox value with the partial string used to filter the listbox.
FEA: ItEr77S15FilteringEnhancements
There was an issue that was causing bandbox search filter in company view to be
cleared, and deleting the corresponding session variable, the second time
that perspective was accesed without changing the filter.
FEA: ItEr77S15FilteringEnhancements
In order to avoid to have the same user in the session twice, the validation
query of User entity has been done in a different transaction.
The issue happens with resources too, so the same solution has been used in
both cases.
FEA: ItEr77S04BugFixing
The new listener registered to track changes on ResourceLoad perspective zoomLevel
was not always being called. An explicit reference was defined to avoid that
listener to be wrongly freed.
FEA: ItEr77S15FilteringEnhancements
This allows to add a task over a leaf in a filtered WBS, and being able to keep
seeing the 3 elements: the new container (with the name of the previous leaf),
the previous leaf without name and the new task added.
It's easier to understand with an example. Imagine you have the following WBS:
* Task 1
* Task 2
And you filter by task name using "2", then you'll have:
* Task 2
Then you select "Task 2" and add a new task called "Subtask A".
Without this patch you'll only see:
* Task 2 (the new container using the name of the old leaf)
|- Subtask A (the new task)
However, it's better you see the following
* Task 2 (the new container using the name of the old leaf)
|- (empty task) (the old leaf that you should rename)
|- Subtask A (the new task)
FEA: ItEr77S15FilteringEnhancements
This will allow to get a already filtered WBS if you have been inside the
project before and you have applied some filters, as the filter is already
stored in the session.
FEA: ItEr77S15FilteringEnhancements
getIssues gets now the issues from jira in one request. This is done by adding a
query fields with desired fields to be included in response. Moreover the max_results
is now outside if(!query.isEmpty) statetment.
Test case is modified to read label from jira-properties instead of hard coded
Since the "foreign key" constraint with onDelete parameter introduced into liquibase is handling
at database level the integrity, the external operations to clean the setting values are not longer
needed.
FEA: ItEr77S15FilteringEnhancements
When you enter the project Gantt view and you have some filters already stored
on session, you had a first rendering with the whole project and then a new one
filtering it. The patch avoids the first rendering.
FEA: ItEr77S15FilteringEnhancements
Add a listener in order to update the value in the session when user changes the
zoom.
For the company view it will use it's own variable to store the zoom level,
inside a project it will use the zoom variable shared for all the project views.
FEA: ItEr77S15FilteringEnhancements
This will allow to get a already filtered WBS if you have been inside the
project before and you have applied some filters, as the filter is already
stored in the session.
FEA: ItEr77S15FilteringEnhancements
The value from session was not been used to calculate the data to show, and it
was only renderer.
The problem was that the method
org.libreplan.web.resourceload.ResourceLoadController.Reloader.reloadInTransaction()
was calling
org.libreplan.web.resourceload.ResourceLoadController.WorkersOrCriteriaBandbox.setup(ResourcesLoadPanel)
after calculating the data to show.
So
org.libreplan.web.resourceload.ResourceLoadController.WorkersOrCriteriaBandbox.buildBandboxFilterer()
was called after it calculates the data to show, so it doesn't take into account
the default values for the selected filters.
Now, the initialization of the bandbox is done in the constructor, and then the
selected filters are marked.
Later the buildBandboxFilterer is called and it only wraps the bandbox inside a
hbox.
FEA: ItEr77S15FilteringEnhancements
