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
In this way it's possible to get all the projects for wich some part of their lenght is
comprehended between the defined start and end dates, with the previous strategy only the
projects which were completely included in the interval were being listed.
FEA: ItEr77S15FilteringEnhancements
This will allow to get a already filtered Gantt 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 database query that filters the orders by several fields is used only when
the subelements checkbox is not clicked. Otherwise the old query is used and the
old behavior is kept for the filtering.
However, if the checkbox is not clicked, the new query is used to get the
initial list and to do the successive filtering too.
NOTE: Resources are never assigned directly to the root element, so if you
filter by resources it'll only work if you have the subelements checkbox
clicked.
FEA: ItEr77S15FilteringEnhancements
