- stage model: add field holding the eventual specific legends for kanban
tates and star (priority) management
- crm.lead kanban: use kanban column using group_by_tooltip
- update data and demo data
- stage model (project.task.type): add fields holding the eventual specific
legends for kanban states and star (priority) management
- project: task now have labels; you may use project to hold trainings
instead of tasks.
- project form: use label field on tasks statinfo to use the label
- project.task form: use kanban state customization using states_legend option;
- project.task kanban: use kanban column and kanban state cuztomization
using group_by_tooltip and states_legend options
- project_issue: issues now have labels, like tasks.
- issue: same kanban custo as for tasks
- update data and demo data
[IMP] web: statinfo widget now take an optional label_field option allowing
to have strings coming from another field present in the form view
The payment term description (note) is meant
to be shown to customers. Restore it in the
default invoice report, as it was in 7.0.
If empty, assume the payment term is meant
to be hidden from customer, and do not show
anything.
By default the description includes the name
of the payment term, so no need to keep both.
the filters menu can quickly grow if the user adds many conditions.
Once it grows out of the screen, the lower buttons can not be reached
anymore. This patch adds a vertical scrollbar to fix this issue. It
has to use some javascript to update its max-height property.
Commit 388732dfa6 introduced a makefile at the root of the project, and
dh_auto_build is using this file instead of setup.py. Explicitely tell
debhelper to not use the makefile.
Raw API documentation is not sufficient for people to learn the working
principles of the API, especially when they already know the old one. And some
things have changed since the opendays so the presentations don't reflect the
current state of affairs.
Closes#3483
So that we can customise the real-time stock journal items made during sale invoice postings for certain companies who account for it slightly differently.
the .oe_background_grey class only changed part of the kanban background
when it was scrolled. This makes sure that the full table has a grey
background.
This revert partially the rev. f2e4a10e1a
File "/home/odoo/src/odoo/8.0/addons/mail/mail_mail.py", line 76, in default_get
if context and context.get('default_type') and context.get('default_type') not in self._fields['type'].selection:
TypeError: argument of type 'function' is not iterable
name was confusing for bom and product if the value of the attribute is display without the attribute name
added key in context to keep the previous behaviour (e.g. in product view where the attribute name is present)
Kanban and form view kanban selection widgets can now be dependent of the
current stage of the record. The displayed legend can be taken directly
from the stage instead of the field selection values.
- added states_legend option on kanban selection widget for kanban and form
view: used to change the selection displayed value by a value coming from the
record given by group_by (kanban) / states_legend_field (form view). This allows
customizing the kanban selection widget depending on stages.
Improved the tooltip of kanban groups customization by improving the first
implementation of group_by_tooltip parameter in kanban view declaration.
This is done by adding some options and improving the first (still not
used) implementation:
- added group_by_tooltip option on field used to group on kanban view. Its
values is a collection of fields on the record used to group. The tooltip of
the group header will be the text formed from those fields values, allowing
custom tooltips for different kanban columns.
- now all data of the kanban columns are fetched in one call instead of doing
one call for each column. The various fields to read are collected by
introspecting the view definition.
Future commits will aim at using those features various addons, notably
in recruitment, project and crm.
Otherwise the Search More view will crash for example for sale order line because it will fetch the price of all products and then try to convert uoms for pricelist rule application without checking uom compatibility
once widget extended with ReinitializeFieldMixin, the event binding with the binary file input and the on_file_change method can be done in initialize_content instead of start
This fix is related to d36c8b5c9b
The add attachment button should be displayed while being in edit mode, but not in view mode
As the widget depends on the form actual mode, the widget should be re-rendered each time the actual mode changes
This is the point of the ReinitializeFieldMixin class
Thibault Delavallée