For example a project with a task of 40h starting on Monday and finishing on
Friday, with a deadline on Friday should was wrong calculated before. Not it
says that the deadline is fulfilled as expected.
FEA: ItEr77S04BugFixing
End date for root task is only updated while saving the project in the method:
SaveCommand.updateRootTaskPosition.
Now the end date is calculated checking the dates of the children tasks and
getting the bigger one.
FEA: ItEr77S04BugFixing
The problem was that now when a user or resource is saved, it's checked the
limit in the configuration fields. For that reason, we need to load the
configuration data before saving any user or resource.
Without this patch the generic allocations were gotten from database, and only
for the criteria in an already stored allocation a replacement for the
allocations in memory was done.
From now on, for each possible criterion, the allocations from database are
recovered, and they are replaced if needed by the new ones in memory.
FEA: ItEr77S04BugFixing
Two changes:
* In project creation pop-up, it's not needed to change the project code when a
template is selected.
* When the project is created from the template, the code used is the one in the
project creation pop-up and not a new one (like it was happen before).
FEA: ItEr77S04BugFixing
When a task is moved in the Gantt, the constraint changes and it could causes
that some of its siblings should be moved, because of the parent element is
moved too.
FEA: ItEr77S04BugFixing
When the start or end constraints for a task are requested, if it's a container,
it'll return the constraints of the children elements too. Except for the case
of the root task (the project) in order to avoid regression described in bug
FEA: ItEr77S04BugFixing
The query was just getting the tasks with parent the order, but not all the
sub-tasks.
A similar code that for the case of imputed hours has been used for the expenses
case fixing the issue.
FEA: ItEr77S04BugFixing
The problem is that SumChargedEffort is null when it shouldn't, so the order is
marked to be recalculated if this is the case.
This is a workaround for the issue described in the bug #1529, while we're not
able to reproduce the problem.
FEA: ItEr77S04BugFixing
Even if this log shouldn't show any message now as the level is set to INFO, but
maybe during development it could be changed to DEBUG to show the log messages.
Date formate was not been localized in the reports, so it has been changed in
order to provide localized dates in the reports too (like in the rest of
LibrePlan UI).
FEA: ItEr77S04BugFixing
* Create new methods in Util class that use DateFormat depending on localte to
convert a date to string.
* Review all the parts of the code where the date format is hard-coded and call
to the new methods.
FEA: ItEr77S04BugFixing
Changes in commit 004dec3a42 where not needed
because of the new maven dependency with jasperreport-fonts already includes the
DejaVu fonts. So we don't need to have any font installed in the system to
generate properly the reports.
That means that we will have one less dependency in the future versions.
FEA: ItEr77S08ReportsFonts
