* website_crm_partner_assign
Before this task, portal section titles were not unified, some titles had
'your', some 'my', some none.
This commit unifies everything.
task-51585
closesodoo/odoo#24697
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Display field in two groups to display in four column.
Plus, email_from is used to 'Allow communication with a customer without
creating a partner'.
Since this field is not very useful, it is best to hide it to clean the UI.
Something was already done at aa33c81535
task-54027
closesodoo/odoo#22845
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
Fixing missed 'pivot_row_groupby' assigned to groupedBy in pivot_model.js in
Load function (Already done in reload function), which was missed in commit
42f22a2.
Added qunit test case for testing correct value.
Apply pivot_row_groupby on user in project
task-54027
Before this PR, if you don't know that we have a website_form module, you will never use it and keep the 80's feature of send an email. Now, it is automatically with website.
Before, when you drop a new form, you just had the default required fields.
Now, you will have default form and will be able to finetune this one.
There still some fixes to do:
- extra_step: restore default value
- contact_form: default value based on request.params
- Refresh optionally data-source of x2many
That's one small step for Odoo, one giant leap for website_form.
See commits to have more details.
task-32212
closesodoo/odoo#32565
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
`t-att-` inside form should be removed because it makes the form not editable
by the form builder.
Instead of having these values set to the `<form>` DOM element, it will use a
`<span>` outside it.
task-32212
Now, the default form already has multiple fields by defult, including
`subject` one.
The test was adding that field, so it now needs to add another one that is not
on the form.
task-32212
That way, it is possible to add the template, fields and success page to
different type of form.
Next commits will use what has been done in this commit.
task-32212
As website_form is now auto installed with website, we want that module to
create a nice form by default but leave the possibility to the user to disable
it.
Wealso want a thank you page in website_form as it now have a nice form on
contact us page.
task-32212
When website is installed, we want website_form to be auto installed so there
will be a nice form available instead of just a href mailto button.
Also, when both website_form and crm are installed, we want website_crm to be
loaded. Removing website_partner dependency do the trick. That dependency seems
to be only historical and not needed anymore anyway.
task-32212
- Purpose of this task is to remove required attribute on HSN field because that is not more required.
- before applied this commit if set up an indian company, we have an error if we edit a product because of HSN field is required.
Related Task: 1948171
closesodoo/odoo#32077
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
Purpose: Add option to set a default warehouse on the website.
Before this: We are showing all quantity of product for specific company not
specific warehouse.
After this: We will see availability of product based on warehouse set on the
website.
task-1913031
closesodoo/odoo#30104
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
This commit applies the correct quotation header to the quotation email.
The header now states "Your Quotation" if the stage is quotation instead of "Your Sale Order".
Related Task ID : 1936003
closesodoo/odoo#30849
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Change the label from PayUlatam to PayU Latam.
Hide s2s Form template field where Payment Flow is not s2s.
task-1940000
closes odoo#31048
closesodoo/odoo#31048
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
Previously, we could only set cover image on the kanban view of project
task. This commit makes the feature generic so now cover image can be
added to any kanban view.
Technical notes:
- field used to display the cover image has to be set as 'data-field'
attribute on the kanban dropdown's menu related to cover image
- developer will have to take care while designing kanban views with
cover image ability in such a way that it does not break the design
Task 32108
closesodoo/odoo#31731
Signed-off-by: Martin Geubelle (mge) <mge@openerp.com>
Basically when someone requests a new car, getting that car ready takes
some time, this means that during the waiting period, that person is
still driving its old car.
This commit adds a field future_driver_id on fleet.vehicle to tackle
that problem and a boolean plan_to_change_car on the partner to track
who wants to change car.
+ Apply some linting to the files
This commit cleans the vehicle form view, the vehicle contract form
view, the cost list view and adds a manager_id field on the
vehicle.model which is then used as a related on the vehicle.
Task: 1930298
closesodoo/odoo#31197
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
hr_prensence add a menu 'reports' in employee app and
hr_contract_dashboard add a 'Reporting' menu.
Merge both together.
closesodoo/odoo#32377
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
This problem appears when the module l10n_be_hr_payroll_fleet is installed with the
dynamic report for employees (enterprise module hr_contract_reports).
This module inherits from hr.contract and will create and modify some fields.
By modifying contract's table, PostgreSQL will drop the view from
hr_contract_employee_report. At the end of the installation, PostgreSQL will
check if tables exist, it isn't the case for the view from
hr_contract_employee_report, so it will recreate it.
It's the normal behavior.
But when a table is missing, a warning is logged and create problem with
Runbot. For this reason, it's better to log an Info and not a Warning message.
Validated with @rco
On the product form view, the stat button computing the quantity on hand
doesn't give the same result as the quants list triggered by this button
What's displayed in the stat button of the quantity on hand ?
1 get the view location of all the warehouses
2 built the generation tree from the view locations
3 get all the quants for those locations
What's displayed in the quants list of the quantity on hand ?
1 get all the quants stored in internal locations
This commit share the same logic for those two views, by building the
generation tree for the view location then filter on internal locations
Task : 1929515
closesodoo/odoo#30501
Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>
Before this commit, the demo data in the
Italian localization would give errors,
because it was setting fields incompatible
with the company being Indian.
It is better not to do this and leave it empty.
(Indian localization is the only to do this)
closesodoo/odoo#32781
Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>
To be able to correctly translate the information message on consumed credits, we are building those message in python in a computed field instead of building in xml with four computed fields.
Task-ID 1965687
closesodoo/odoo#32676
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
[IMP] mail: Delete tracking values when uninstalling module
--------------
### Purpose
mail.tracking.values should be deleted when the corresponding field is deleted (when the module which defined it is uninstalled).
Firstly because we don't want useless data in db.
Secondly because the groups associated with the field can no longer be checked if it was deleted. As we don't know to whom the value was restricted, the value should not be displayed anyway.
Note: this case was fixed in saas-12.2 by b9e96b7 but the proper
way to fix it is to delete the tracking values.
### Specification
Delete `mail.tracking.value` when the associated `ir.model.fields` is deleted.
Two alternatives were considered:
1. Change the `field` field of `mail.tracking.value` from Char to a m2o to `ir.model.fields` which allows to use delete oncascade. This implies to modify existing code, but more importantly it adds database queries.
2. Override the unlink method of `ir.model.fields` to first unlink associated tracking values.
The first method is probably cleaner but the second method was nonetheless chosen as we don't want to impact performance in the main tracking flow only to better support module uninstalls which happens rarely.
Note: when a module is uninstalled, `ir.model.fields` are unlinked one by one (in a for loop). Tracking values are therefore also unlinked field by field. Batchifying field deletion would greatly reduce the amount of queries.
[IMP] mail: Rename groups field of mail.tracking.value
----------------
This commit renames the `groups` field into `field_groups`.
The previous name was impossible to grep as the word `groups` is everywhere in the code base.
Also the new name better follows the implicit convention that fields related to the tracked field all start
with `field_`.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
closesodoo/odoo#31861
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Before this commit, payment journal "Available in PoS" should not
ticked by default if created from PoS. And if I remove the filter
"Available in PoS", I should not see all payments methods.
Now, payment journal "Available in PoS" is ticked by default if
created from PoS. And if I remove the filter "Available in PoS",
I should see all payment methods.
closesodoo/odoo#30748
Signed-off-by: Quentin Lejeune (qle) <qle@odoo.com>
Currently, in small devices, hamburger menu of the cloned navbar
is not scrollable due to fixed position.
This commit improves the behavior and makes the affixed navbar
scrollable, enabling user to navigate through all the available
menus.
task-1938637
closesodoo/odoo#32359
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Currently, if a message does not have any tracking
value, any attachment and no body BUT has a subtype
with a description, the message is not considered
as empty.
The message subtype should not influence its
"emptyness".
This commit renames the `groups` field into
`field_groups`.
The previous name was impossible to grep as
the word `groups` is everywhere in the code base.
Also the new name better follows the implicit convention
that fields related to the tracked field all start
with `field_`.
Purpose
=======
mail.tracking.values should be deleted when the corresponding
field is deleted (when the module which defined it is uninstalled).
Firstly because we don't want useless data in db.
Secondly because the groups associated with the field can no longer
be checked if it was deleted. As we don't know to whom the value
was restricted, the value should not be displayed anyway.
Note: this case was fixed in saas-12.2 by b9e96b7 but the proper
way to fix it is to delete the tracking values.
Specification
=============
Delete `mail.tracking.value` when the associated
`ir.model.fields` is deleted.
Two alternatives were considered:
1. Change the `field` field of `mail.tracking.value` from Char
to a m2o to `ir.model.fields` which allows to use delete
oncascade. This implies to modify existing code, but more
importantly it adds database queries.
2. Override the unlink method of `ir.model.fields` to
first unlink associated tracking values.
The first method is probably cleaner but the second method
was nonetheless chosen as we don't want to impact
performance in the main tracking flow only to better
support module uninstalls which happens rarely.
Note: when a module is uninstalled, `ir.model.fields`
are unlinked one by one (in a for loop). Tracking values are
therefore also unlinked field by field. Batchifying field
deletion would greatly reduce the amount of queries.
There is a button on the employee form that show the number of
contracts. This button is only accessible for hr manager,
but not for contract manager.
It's make more sense that this button is accessible for contract
manager. The contract manager can already see all contract from
the menu. Hr manager inherit rights of contract manager.
With this commit, the button is accessible with contract manager
rights and hr manager.
closesodoo/odoo#31415
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
In Belgium, we have the concept of time credit and parental leaves.
Globally the person keep full time rights and the initial contract
is always signed on a full time basis. But an avenant with the new
time schedule must be signed.
A new wizard on contract allows to manage credit time. We can
specify the start and stop date, the new calendar and the work
time ratio. The new wage will be computed.
After validation, the current contract will be duplicate two times,
one modified for the time credit contract and the second for after
the time credit period. The current contract will have end date at
the beginnig of the time credit period.
TaskID: 1924200
* Use === for stricter comparison.
* Merge checks on this.wysiwyg and this.mode as they are redundant in
this case.
Task-ID: 1950784
closesodoo/odoo#32280
Signed-off-by: Pierre Paridans <pparidans@users.noreply.github.com>
The original issue appeared in mass_mailing where triggering the mail
template preview throws a client error.
This commit prevents commitChanges() from being called before the
element is rendered.
Task-ID: 1950784
When a employee succeed a course or a certification, a new line
will be added in resumé of employee profile.
+ [FIX] hr_skills: remove sequence to sort resumé
Actually, sorting a resumé doesn't work because we add new line for
title in the array.
With this commit, all sequence are removed. The resumé is sorted
by date and skills are sorted by level.
closesodoo/odoo#31764
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
When the assets are loaded, the `hr_timesheet.timesheet_uom` scope is
loaded in order
to bind the `timesheet_uom` to the correct already existing widget (defined
in the session, like `float_time` or `float_factor`, ...).
The problem is that in normal mode (not debug assets), when the binding is
done, the field_registry is empty, so the correct base widget is not applied.
The fix is to add the scope filling the registry in the requirements of the
`timesheet_uom` scope. Strangely, it was working in debug assets mode.
closesodoo/odoo#32736
Signed-off-by: Jérome Maes (jem) <jem@openerp.com>
Before this commit, runbot-theme was red somehow for the geoip pricelist test.
Adding post_install seems to fix the issue, anyway it is better to flag the
tests as such as it make no sense to test pricelists during module install.
closesodoo/odoo#32727
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Before this commit, the gengo private password was displayed in
plaintext in edit mode. This is due to text fields being rendered as
`textarea` in edit mode, which does not support the "password" type.
This commit fixes the issue by turning this field to `Char`, so that
it is rendered as `input` with type "password" in edit mode.
The loss of multi-line from `textarea` is not a big deal, because
gengo passwords are not that long.
Task-ID 1892058
closesodoo/odoo#32725
Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
This commit adds facility to showcase product videos on it's
eCommerce page. They can be added to 'product.image' model,
same as extra images, thus allowing user to enter multiple
videos per template and per variant. Also, associated image
will be used as a thumbnail for the video on the product's
website page.
task-1945483
closesodoo/odoo#32298
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
This commit adds a new file 'tools.py' that can contain
utility methods which can be used at more than one places.
For now it contains a method 'get_video_embed_url', that
will accept a URL for the video and return an iframe snippet
that can be embedded if the provided URL is valid (returns
False otherwise).
task-1945483
In this commit, we have changed behaviour of SEO dialog. Now when you
keep title and description fields empty, then the page will use default
title and description. We have added default_title and default_description
to render the preview with default values when title and description
fields are empty in SEO dialog.
Task ID:1949636
closesodoo/odoo#32449
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>