[18.0][MIG] mail_composer_cc_bcc_account: Migration to 18.0#4
[18.0][MIG] mail_composer_cc_bcc_account: Migration to 18.0#4
Conversation
|
|
076cde7 to
3e395d9
Compare
|
@trisdoan I will happily review and test this module once is ready |
|
Hi @trisdoan, I would like to test this module. Could you please rebase to reload the runboat? Thanks |
3e395d9 to
5f7f087
Compare
|
Could it be possible to merge this? |
|
Hello @pedrobaeza, could you merge this please? |
|
A review by a PSC is needed. |
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
|
Can someone comment on the timeline for this module to be reviewed? |
|
maybe @StefanRijnhart can merge it? |
StefanRijnhart
left a comment
There was a problem hiding this comment.
Looks like adding cc/bcc to sending by batch is left out here (account.move.send.batch.wizard)? If so, please mention in the roadmap.
|
/ocabot migration mail_composer_cc_bcc_account |
|
There's no issue in this repo with the title 'Migration to version 18.0' and the milestone 18.0, so not possible to add the comment. |
|
any news? |
ChristophAbenthungCibex
left a comment
There was a problem hiding this comment.
Code LGTM and tested the module and it works well
Note
Changes in 18.0
https://github.com/odoo/odoo/pull/180212=> So, instead of patching
account.move.send, adding cc/bcc support inaccount.move.send.wizard