[19.0][MIG] stock_picking_report_custom_description: Migration to 19.0#464
[19.0][MIG] stock_picking_report_custom_description: Migration to 19.0#464miguel-S73 wants to merge 28 commits intoOCA:19.0from
Conversation
* README by fragments * Remove models * Fix report templates [UPD] Update stock_picking_report_custom_description.pot [UPD] README.rst
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: stock-logistics-reporting-16.0/stock-logistics-reporting-16.0-stock_picking_report_custom_description Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-reporting-16-0/stock-logistics-reporting-16-0-stock_picking_report_custom_description/
Currently translated at 100.0% (2 of 2 strings) Translation: stock-logistics-reporting-16.0/stock-logistics-reporting-16.0-stock_picking_report_custom_description Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-reporting-16-0/stock-logistics-reporting-16-0-stock_picking_report_custom_description/es/
Currently translated at 100.0% (2 of 2 strings) Translation: stock-logistics-reporting-16.0/stock-logistics-reporting-16.0-stock_picking_report_custom_description Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-reporting-16-0/stock-logistics-reporting-16-0-stock_picking_report_custom_description/it/
By default the sale description is set as
f"{product_name}\n{description". If we pass that string as the
description_picking, when we print the report, the name will be
duplicated. To avoid that effect, we want to trim the product name from
the description passed to the picking by default.
TT52044
It isn't very common to write the name in batch. Anyway it would lead to errors in it's current shape. TT52171
7535ebc to
f6c3ae1
Compare
f6c3ae1 to
90d412d
Compare
|
This PR has the |
|
@OCA/logistics-maintainers Please, can you review/merge this PR? |
|
/ocabot migration stock_picking_report_custom_description |
|
/oca merge nobump |
|
/ocabot merge nobump |
|
What a great day to merge this nice PR. Let's do it! |
|
@hparfr your merge command was aborted due to failed check(s), which you can inspect on this commit of 19.0-ocabot-merge-pr-464-by-hparfr-bump-nobump. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
Standard migration to 19.0