The workaround I propose instead of this 'button_restart' hack, and short of reverting rev 1634, is to allow mrp.procurement.action_confirm() to also confirm draft stock.moves, not just 'waiting' ones. This change also seems sensible and correct to me.
The patch is trivial but I still need a test case before landing it on stable. Hopefully I will be able to do that tomorrow before 5.0.7.
As explained in the merge proposal review:
The workaround I propose instead of this 'button_restart' hack, and short of reverting rev 1634, is to allow mrp.procurement .action_ confirm( ) to also confirm draft stock.moves, not just 'waiting' ones. This change also seems sensible and correct to me.
The patch is trivial but I still need a test case before landing it on stable. Hopefully I will be able to do that tomorrow before 5.0.7.
See attached patch if you can help test it.