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
The task is marked as fixed if it has been updated from timesheets even in the
case that dependencies have priority and it should be moved to a different
position. The dependencies will appear as violated.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
* 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
It has been added a new method ICommand.isPlannerCommand() to define if a button
should be added in the planner toolbar or in the common toolbar (save and cancel
buttons).
For the moment, we are using a hard-coded value to know how many buttons we
should add in the plannerToolbar. At this moment we have 2 buttons: reassign and
adapt planning.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
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 you just filter by labels/criteria and you don't choose any specific project.
You were able to see tasks from projects that you are not allowed to read. Now
this is fixed.
FEA: ItEr77S09WBSReport
If you generate the report and afterwards you report some expenses in a project,
the MoneyCostCalculator cache still keep the previous value for the report.
Now the MoneyCostCalculator cache is reseted every time the report is generated.
FEA: ItEr77S09WBSReport
