security calculation checks the validation state of the Assignment, but it should also check if it is expired or not started yet.

This merge request applies fix, extending tests to re-produce and test the situation.
Also, a cleanup in erp5_core: extension.erp5.StandardSecurity.

/reviewed-on nexedi/erp5!548

This is equivalent to work done for Leave Request, at:
185285c4
(merge_request 493)

Follow a simple / non-simple approach, like for Task and its lines.

In default case, user would need only one Presence Request Period, which can be edited directly on PresenceRequest_view. So, in this case, hide the Listbox containing the Presence Request Periods and have default_presence_request_period being created / edited on background, which will acquire quantity, resource, start_date and stop_date from what is set at the view of the Parent.
In case one or more Presence Request Period are added manually, user would get listbox with sub-objects, and editing should be done directly on them, i.e. fields like my_default_presence_request_period_start_date will be disabled fromPresenceRequest_view.

Additionally, now Presence Request has its own:
start_date: equal to the minimum start_date of all Presence Request Periods
stop_date: equal to the maximum stop_date of all Presence Request Periods

These values are set by interaction on Presence Request Period, triggered on setStartDate, _setStopDate. This helps so that presence_request_module listbox can have sortable dates.

Commit contains also test

/reviewed-on nexedi/erp5!541

/reviewed-on !551

It is defined in Portal Type and projects do use versions of it.
Add it as empty in generic implementation, since otherwise the portal type
is unusable (cannot create new documents)

preferences icon (main menu) : f1de (sliders)
sort asc (icon in listbox header) : f160 (sort-amount-asc)
sort desc (icon in listbox header) : f161 (sort-amount-desc)
configure icon (new "configure" listbox button) : f0ad (wrench)
hide (hide button in listbox) : f2a8 (low-vision)
worklist (main menu) : fOae (tasks)
link (relation string field) : f090 (sign-in)

/reviewed-on nexedi/erp5!550

- Remove unused imports and variable
- Do not have empty list as argument default
- Allow object as redefined-builtin in pylint, for the lines it is used
Note: this variable is not anywhere and it should be 'self', but
I do not want to break callers

commit also extends tests in testErp5Security to reproduce the case

mostly uncommited Pylint complains

erp5_test_result: configure correctly TestResultModule_viewTestResultList in order to use a datefield for rendering in new ui

erp5_forge: configure correctly BugModule_viewBugList in order to use a datefield for rendering in new ui

an editable field may be defined in proxy form

/reviewed-on nexedi/erp5!528

Allign with Leave Request Period

This is equivalent to work done for Leave Request, at:
185285c4
(merge_request 493)

Follow a simple / non-simple approach, like for Task and its lines.

In default case, user would need only one Presence Request Period, which can be edited directly on PresenceRequest_view. So, in this case, hide the Listbox containing the Presence Request Periods and have default_presence_request_period being created / edited on background, which will acquire quantity, resource, start_date and stop_date from what is set at the view of the Parent.
In case one or more Presence Request Period are added manually, user would get listbox with sub-objects, and editing should be done directly on them, i.e. fields like my_default_presence_request_period_start_date will be disabled fromPresenceRequest_view.
Additionally, now Presence Request has it's own:
start_date: equal to the minimum start_date of all Presence Request Periods
stop_date: equal to the maximum stop_date of all Presence Request Periods
These values are set by interaction on Presence Request Period, triggered on setStartDate, _setStopDate. This helps so that presence_request_module listbox can have sortable dates.
Commit contains also test that should make it easier to understand.

[erp5_core] Remove quantity input field from category view form. Do not input quantity on category and use quantity unit conversion module instead.

[erp5_configurator_standard_categories] Use quantity unit conversion module to define quantity of category and stop using quantity property on categories.

To take into account organisations with multiple establishments and module containing DSNs for other organisations

Only quantity should be set

Proof is indeed it already changed

And update the related view

/reviewed-on nexedi/erp5!544

This reverts commit e1fa7611.
The fix was already provided by c1b8fa1a