Since commit 2bd10fa757 when the user specify a MO the
unbuild use the existing moves raw and moves finished in order to create the unbuild
moves. In this case the bom_id and the product_id is not needed since we don't generate
unbuild move from the BoM
This commit is related to task ID 39843.
The purpose is to help the user if he has difficulties
to know the purpose of a field. The field for tracking
was named lot but it is also used for serial number. That
could be confusing for the end user. Also rename source as
source location in order to be coherent with destination
location
This commit is related to task ID 39843.
Impacted modules: sale, sale_timesheet, sale_expense
The purpose of this commit is to remove harcoded list of xml ids that
are not defined in the module 'sale'. This commit brings a new
implementation of the feature (hiding re-invoice policy on product
form view, depending of multiple user groups). The approach is more
modular and easy to extend than the previous one.
Therefore, this commit is completely technical and does not change any
functionnal behavior.
Task-1896095
closesodoo/odoo#28786
Modifying a source term in an XML/HTML translated field can lose translations
if the same term is translated in several languages.
closesodoo/odoo#29082
Purpose : This module was allowing to quickly create tasks from
leads. It is now considered as useless, and an activity should be used
instead. We bring another module crm_helpdesk in enterprise to convert
leads to helpdesk tickets, which appears more useful.
Closes#28425 Task-1867574
Before this commit, it was not possible to effectively limit the available
products when a company had several POS with different product offers.
This commit allows limiting the available product categories for a single POS.
Now, a company can serve different POS with different product offerings.
Anecdotal Note: This was especially annoying as the POS only shows 100 products.
If those happened to be the products not served by a signle POS, the only work
around was using the search bar (on a tablet?!?)
closesodoo/odoo#28393
There are two different icons on bom lines to distinct the ones having
attatchement links and the ones without. But those icons are not very
explicit and so we set the same icon for all lines and the number of
documents next to it.
TASK-ID: 1878242
closesodoo/odoo#26625
There is no company_id field on stock.move.line and it is so impossible
to restrict easily the access rights on move lines (except by passing
through stock.move, but all stock move line don't always have a
stock.move)
To resolve this we've added a field company_id on stock.move.line, and a
constraint to force it having the same company_id than the one on stock
move.
Task ID : 1905232closesodoo/odoo#28575
Until now, the volume measure displayed on the product form was only in
m³. We now allow to choose between m³ and ft³.
So, we add volume selection field (m³/ft³) on general settings and it will
be display on product and product variants form view as configuration.
We also Remove tooltip from weight and volume field.
And display weight (kg or lb(s)) in product and product variants form view correctly,
because currently weight didn't display on product form view before save the product
but after this commit weight will be display.
This commit is related to task ID 1869002.
closesodoo/odoo#26542
-Ticked by default(Update quantities on SO/PO)
-Hidden in debug mode
-Rename label "To Refund (update SO/PO) into Update quantities on SO/PO"
This commit is related to task ID 1880715 and closes PR #28091.
The purpose of this PR is to allow more flexibility on Manufacturing.
It will allows:
- Pull and Push rules are no more directly trigger. It will require a confirmation from the user in order to launch them. (except when it comes from another rule)
- The user will be able to add extra components. Those components will follow the classic flow (trigger rules, will be present in workorders and produce wizard, ...)
- State will be computed and will not require explicit write
- Advanced filter
Task 1889384
closesodoo/odoo#28034
Before this commit, the placeholder was hardcoded:
'Drag building blocks here'
Now you can customize the placeholder using a data-editor-message attribute.
The purpose is to be able to plan manufacturing order
without propagate the components's documents directly.
Except when the manufacturing comes from a pull rule, it will
be confirmed directly.
In order to do it, it will just create the moves without confirm them.
They will be only confirmed after a 'Mark as Todo' click.
Refactor production order state:
- Directly have an idea of linked workorders's state
- Computed in order to manage it in a single method
- Add tooltips for each state
Remove the None in availability selection field instead use a False
Also refactor the ready_to_produce field in order to only set as
assigned a production order that have the component for its first
workorder.
Historically, the `website_sale.product_attributes` was a customize option.
That template became a normal view (removed customize_show attribute) with
bbd2d0e42
As it is now a normal view, there is no reason left to be an xpath view and we
can move itw code directly into the inherited template.
That way, we can simplify the `website_sale_comparison.product_attributes_body`
template that was doing a cross xpath (inheriting `website_sale.product` but
xpathing a DOM element from `website_sale.product_attributes` which was also
inheriting `website_sale.product`).
Note that cross xpath was not working well with multi website but was fixed
with 410c07283b
Still, we should avoid doing cross xpath when possible (originally it was not
possible since the view was a customize_show) as it is hard to grep DOM element
to find possible breaking xpath when doing changes on DOM.
This is the reason of this commit.
closesodoo/odoo#29044
We restrict the case of locations that can be scrap locations to
locations of usage internal or inventory loss, depending on how you want
to manage your scrap. Other usage of location shouldn't be scrap
locations.
TASK-ID: 38469
When a location is archived, we are checking that it is not used a
warehouse stock or view location to avoid bad configration leading to
inconsistencies on stock available quantities.
TASK-ID: 38469
As configuring multiple vendor locations is a quite advanced case, that
need too change configuration on partners, and eventually routing, we
remove those demo data that can lead to misunderstanding the way vendor
locations works.
We've also adapted a test that was using those demo data
TASK-ID: 38469
The field partner_id on locations is not used in odoo, and can create
some confusion in odoo with the customer/supplier location you can set
on your partner and/or the owner_id you can set on your moves ans
quants. So we removed it.
TASK-ID: 38469
The stock location usage 'procurement' is not used anymore in stock, and
we remove it as it is not used either for the stock and valuation of
stock.
TASK-ID: 38469
Purpose : When we create order point in another company, it is not setting name ( sequence ).
After this commit it will use ( sequence ) in all company, as we not set company_id on the sequence of order point.
Task #1908526Closes#28597
In this commit use the python constraint to check the accounts if they are duplicate.
This change is because before this configuration there will be an entry cancelling another one in the same account,
resulting in a not impacted valuation account.
This commit is related to task #1908065.
closesodoo/odoo#28604
The sales tab is displayed on product form even if there are no modules
that need it are installed and no fields are displayed in it.
It has been introduced in this commit: https://github.com/odoo/odoo/commit/8e40fed7734793178e4b661a2b28a7f36f8ff626
that we revert and fix by adding an xpath in the point_of_sale module
that display the sales tab when point_of sale_module is installed (even
if sale module is not installed.
Task ID - 1893455
closesodoo/odoo#28176
* survey, website_slides
While not changing their name or their amount, this commit reorganizes
the assets helpers to:
Avoid all file duplicates in different helpers
----------------------------------------------
Before, we had to put some files in different helpers, like our
bootstrap mixin overrides which were in the _assets_utils template and
in the _assets_bootstrap template.
Enforce the use of an helper when using bootstrap
-------------------------------------------------
Bootstrap functions, variables and mixins are now out of the
_assets_bootstrap template, which now only contains bootstrap css rules
and our bootstrap fixes and extensions.
Allow using the correct bootstrap utils in all assets
-----------------------------------------------------
In some assets (especially editor ones), we may want to use bootstrap
variables even though bootstrap is not included in those. This worked
before but using *default* bootstrap variables. Now, our overrides can
be properly included if necessary.
Note: this commit may also be a first step to allow for backend
bootstrap and frontend bootstrap to co-exist.
closesodoo/odoo#28204
This merge adds the support of drag/drop files in a conversation
(discuss, document chatter and chat windows).
It also adds helper functions to simulate drag/drop with files in test
environments.
Task-ID 32469
closesodoo/odoo#18914
This commit adds test helper functions to drag and drop
files:
- `createFile`: create a file that can be used for drag and
drop in tests.
- `dragoverFile`: to drag a file created from `createFile`
over a DOM element.
- `dropFile`: to drop a file created from `createFile` on
a DOM element.
These utility functions are available from `testUtils.file`.
Example of usage:
```js
var testUtils = require('web.test_utils');
testUtils.file.createFile({
name: 'text.txt',
content: 'hello, world',
contentType: 'text/plain',
}).then(function (file) {
testUtils.file.dragoverFile($el, file);
testUtils.file.dropFile($el, file);
});
```
By this commit user can upload attachments by drag and drop in chatter composer.
This feature can be used from discuss UI, chat windows and form view chatter.
Before this commit chatter unlinks the attachment if another attachment uploaded
with same name. Criteria for removing duplicate attachment is changed with this
commit. Now it will remove the attachment based on name and size of attachment.
The reason for this change is, when you upload image with same name from different
directory with old condition it was not possible to attach more then one image/file
of same name.
Related to task #32469Closes#18914
If multilocation is active then display 'source' location in tree views.
Also in tree views rename the source location to 'From' and destination location to 'To'
Task #1872294Closes#26380
Andrea Ulliana