If a treeitem is selected and a new element is added, the selected item
is converted into a container (newObject) and the selected item is
promoted to a child od this new container.
The criteria of the original element is copied to new element
(container) and removed from the original element. This causes that the
child has a new IndirectCriterionRequirement, which is a new object.
The error happened when doing a reattachment of the Order being this new
IndirectCriterionRequirement a transient entity.
Finally, we have decided to change the business logic of how
criterionRequirements are copied when a treeitem is promoted to a
container. What happens now is that the original item retains its
criterionRequirement and the newObject(container) has empty
criterionRequirements.
FEA: ItEr74S04BugFixing
Added delete button in list of type of work hours. A 'type of
work hour' cannot be removed if it's being used by an 'hours cost'.
FEA: ItEr74S04BugFixing
When it changes the advance type, the previous indirect advances in its ancestors
are deleted and the new one is added if not exists any indirect or direct
advance with the same type.
ItEr73S04BugFixing
When an allocation can not be satisfied keep the old resources per day
and not update them from data. Thus when moving a task back to a place
where it's satisfied the resources per day of the last satisfied
allocation are used.
If a reassign fails, the error is catched and reported so it doesn't
prevent all the load of a project.
This allows to restore checkNoAllocationWithZeroResourcesPerDay and
thus the ignored test can be used again.
I refactored the code that does the checking in the business layer.
Instead of putting it directly in a method executed by
HibernateValidator I put it in a static method in the business layer.
This way it can be reused easily from the view layer.
The validation returns a ValidationException pointing to the object that
caused the error. Its corresponding component is localized in the view
and the error is shown as a WrongValidationException.
FEA: ItEr73S04BugFixing
- Sort the imputed hours rows by date.
- Add a column with the hours type.
- Group in a row all the hours of the tuple (Resource, Date, Hours type) so
that the hours of a row can be an addition.
- Fix the height of the area for the hours with a scroll to avoid layout
problems.
FEA : ItEr72S04BugFixing
- Add a new column with the date.
- Rows grouped by two columns (type of hours,date).
- Change the title of the report to 'Costs by resource'.
- Change the order of the columns task code and task name.
- Add the code of the project to the project line.
FEA : ItEr72S04BugFixing
The activation periods of the Calendar assigned to the Resource were not
being considered when doing a limiting allocation.
A gap should be constrained according to the activation periods of time of
the Calendar.
FEA: ItEr71S04BugFixing
