Now the IntraDayDates methods are used. Most of the changes are in the
tests, since they were using the previous LocalDate methods.
FEA: ItEr77S04BugFixing
Depending on selected node and if it's or not updated from templates the
different buttons are enabled or disabled accordingly.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
The methods used to calculate the start and end of the task when
moving the task and when allocating in the form were different. This
caused the length of the task to change when being moved.
Now the method used when moving the task is the one always in use,
because it's more precise.
When doing the allocation that calculates RESOURCES_PER_DAY use
IntraDayDates instead of LocalDate so if the first day of the
allocation is partially allocated, the part free is used.
FEA: ItEr77S04BugFixing
* TaskElements are marked or not as updatedFromTimesheets
* TaskElement start date is set with a START_IN_FIXED_DATE constraint to the
first date in the timesheets
* TaskElement end date is set to the last date in the timesheets if this is
later than the current end date of the task
* Depending on if the task is marked as finishedFromTimesheets, a progress of
type TIMESHEETS is added or not. If the task is finished, the end date is set
according to last date in the timesheets
* TaskElement size and position is updated in the Gantt
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
In that way we are sure that everything is removed properly. We have to manually
detach the removed element from its parent in order to avoid delete the parent
too.
FEA: ItEr77S13AllowDeleteOrderElements
The new progress type is read-only, so a new field to mark it in AdvanceType has
been added and used in the UI accordingly.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
In order to do that, a set of order elements affected by the lines
added/edit/removed in a timesheet is calculated before saving the timesheet.
Afterwards the first/last dates are recalculated for all the order elements in
the set.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
The first and last date of the task depending on the timesheets will be stored
in these two new fields in SumChargedEffort.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
In
ExpenseSheet.checkConstraintPersonalExpenseSheetMustHaveTheSameResourceInAllLines
we check that the resource is the same in all the lines. However, if there are
no lines an exception arises.
FEA: ItEr77S04BugFixing
If any child has the filtering criteria invalidated, it's not taken into account
in order to calculate the values in the parent task that is part of the report.
FEA: ItEr77S09WBSReport
The tasks that will appear in the report are the ones that have directly
assigned all the labels, so the children will be hidden.
FEA: ItEr77S09WBSReport
Modify entry points converters for entities extending IntegrationEntity in order
to use code instead of id. In that way user can see the code in the UI without
having to query the database.
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.
