Criterion satisfactions were being stored more than one because of them were
being processed before checking worker ID:
assignedCriterionsModel.confirm();
FEA: ItEr69S04BugFixing
The previous listeners associated to the recommended allocation were
not removed, so pressing the recommended allocation button caused it
to be executed several times.
FEA: ItEr69S04BugFixing
Allocate element at correct position if day constraints required an
appropriative allocation
Reschedule elements affected by an allocation to avoid dependencies violations
FEA: ItEr69S04BugFixing
Inside the task's bounds the allocations can grow until reaching
task's bounds but they can't shrink, i.e. the allocating zero hours
the last day would keep the same end date.
FEA: ItEr69S08AdvanceAllocationFix
The problem lied in that the @NotNull annotation was applied to a
field. This is dangerous because if the object that is being validated
is a proxy, the value is always null. Now the annotation was moved to
the getter.
FEA: ItEr69S04BugFixing
Otherwise if an exception happens it would tell the user that the
allocation has been saved, when in reality it hasn't been saved due to
the exception.
FEA: ItEr69S04BugFixing
Execute the next SQL sentence in your database if you want to keep working with
your current database:
UPDATE DATABASECHANGELOG
SET MD5SUM='3:b6640208fbf11943fa46d8953516bad7'
WHERE ID='replace-column-limited_resource-with-resource_type' AND
AUTHOR='jaragunde' AND
FILENAME='src/main/resources/db.changelog-1.0.xml';
FEA: ItEr68S04BugFixing
The invalid ranges mechanism is not suitable when the invalid dates to
specify are potentially infinite.
An additional mechanism is added allowing to veto some of the dates.
FEA: ItEr68OTS05IntroducionLimiteSobreasignacionCalendarios
Now the extra effort properties are respected. The code is simplified
since there is no longer needed special handling for exceptions.
FEA: ItEr68OTS05IntroducionLimiteSobreasignacionCalendarios
Now these two components support a new attribute 'behaviour'.
This attribute defines how the search components should work. For
instance, non limiting search is configured to allow multiple selection
and search only for non limiting resources. On the contrary, limiting
search only allows to pick one resource.
New behaviours could be added in the future, or support new
functionality, for example, allow to select only specific resources, for
instance.
FEA: ItEr68OTS03XestionRecursosEstratexicosItEr67OTS03
This replacement has implications in higher layers and makes the application
crash, but changes are separated in several patches to improve their legibility.
In this patch, we modify the DB, the DB update system and the entities in the
bussiness layer.
FEA: ItEr65OTS07XestionRecursosEstratexicos
