Pricelists are not correctly used when creating a quotation using a quotation template

[HarlekinSimplex]

Impacted versions:
odoo 13 CE with website

Steps to reproduce:

• Create a pricelist with a special price for a certain product to be offered in the quotation
• Add another product to this pricelist to be offered as optional product in the quotation
• Assign that pricelist to a customer
• Create a quotation template with the product and the optional product that are priced in the pricelist
• Create a new quotation with customer and pricelist set
• Select quotation template to fill product lines

Current behavior:
Standard product prices are used for the quotation lines
Pricelist prices are used for optional product lines

Expected behavior:
Prices as defined in the pricelist should be used for product and optional products

Additional Information:
Issue may relate to recent changes on qoutation template price handling.
See: No price unit in quotation template #47186

[pedrobaeza]

Not sure this is a bug or the prices are intended to be kept from the quotation.

@dbo-odoo can you tell us?

[HarlekinSimplex]

I tried the following workflow:
1.) Create a new blank quotation at the backend
2.) Select customer (His Pricelist was selected automatically as set up at the partner form)
3.) Add the products by selecting a quotation template for a quite complex quotation with 4 products and 3 optional products

So there were no other products or prices to be kept before selecting the quotation template in that quotation. For me thats the logical flow to create complex qoutations where the use of quotation templates makes a lot of sense.

Currently the wrong prices are pulled from the database.
So I have to lookup the proper prices manually or just delete all products inserted by the template and start over from scratch adding them manually.
Btw adding products manually pulls the correct prices from the pricelist into the quotation.

So if the actual behavior is intented, imho quotation templates make no sense at all.
Actually I tested that with quotations created with the backend only.
Maybe it works properly with quotation templates used from the frontend.