This makes the component fit inside the day and overlap when the zoom is
wide enough to make the interval thinner than the sum of the marker widths.
FEA: ItEr77S04BugFixing
The latest versions of some browsers were about to drop compatibility
whith these prefixes, so just the Candidate Recommendation is kept.
FEA: ItEr77S04BugFixing
This is done using the entry point /planner/index.zul;order=order-code which also helps
browser history management to enable bookmarking, refreshing or use the back button.
The link to the taks from the project view is not added due to an interaction it has with
the system to prevent from leaving the current URL, which would need to be written with anchors
to avoid this interaction.
FEA: ItEr77S03Community
They were only calculated when you visited the dashboard perspective. Now they
are calculated always when you save the project.
FEA: ItEr77S04BugFixing
When the date in the legend was modified, all the checkboxes were removed and
created from scratch. Now it is set an id for the labels associated to each
textbox and its value is updated accordingly when changing the date instead of
create them again.
FEA: ItEr77S04BugFixing
The popup is opened with double-click or ENTER and you can close it with the
button or clicking outside of it.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
When you set the days for a task, even if it does not have consolidations, the
method does not allow you to move it before the start date. This restriction has
been removed.
FEA: ItEr77S04BugFixing
In order to allow switch tasks codes and avoid the issues changing the code
while creating a child, the unique constraint in DB for field code in
order_element table has been removed.
Instead two new constraints methods have been added:
* OrderElement.checkConstraintUniqueCode()
* Order.checkConstraintUniqueCodeInsideOrder()
FEA: ItEr77S04BugFixing
Both bars will work like the money cost bar was already working.
The change is done due to the problem that appears when you adapt the planning,
and some planning remains before the start of the task. In that cases the bars
were not being printed properly.
Moreover current implementation was quite complex, and even if it gives some
useful information in specific cases, it also causes some misunderstandings to
the users.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
The comparison with the OrderElemen was wrong and it causes that the data stored
was wrong.
Moreover, it was not needed to open the transaction in the bound service method
as it's already opened in PersonalTimesheetModel.
FEA: ItEr77S14BoundUsersWebServices
This is needed when you for example remove a timesheet for task, and the task
was previously updated and marked as finished with the information from the
timesheet. If you adapt the planning again you need to remove the TIMESHEETS
progress accordingly.
FEA: ItEr77S12AdaptPlanningAccordingTimesheets
